Implementation and Experimentation Status in Chromium
April 5, 2023 ยท View on GitHub
This page tracks the implementation and experimentation status in Chromium of different features of the various Scheduling APIs. For more information on the various APIs and their statuses, please see the repo's README.
Features and Minimum Versions
Experimental Features
| Feature | Flag(s) | Minimum Version |
|---|---|---|
scheduler.yield() | SchedulerYield | 113.0.5672.24 |
TaskSignal.any() | AbortSignalAny | 112.0.5599.0 |
Shipped Features
| Feature | Minimum Version |
|---|---|
scheduler.postTask() (Window and Workers) | M94 |
TaskController and TaskSignal | M94 |
prioritychange events and onprioritychange | M94 |
| TaskPriorityChangeEvent | M94 |
Local Testing
There are two ways to enable the experimental scheduling features in Chrome:
Method 1: Enable all experimental web platform features by navigating to
chrome://flags/#enable-experimental-web-platform-features
Method 2: Enable just the desired scheduling features by passing the appropriate flags at the command line, for example:
--enable-blink-features=SchedulerYield
Origin Trials
No Origin Trials for scheduling
APIs are currently running, but an Origin Trial for scheduler.yield() is being
planned for sometime in 2023 Q2.
Examples
Sample code can be found in the explainers.
Filing Issues
For API issues or concerns, please file a GitHub issue.