Prototype Scheduler.yield
Categories
(Core :: DOM: Core & HTML, task)
Tracking
()
Tracking | Status | |
---|---|---|
firefox139 | --- | fixed |
People
(Reporter: sefeng, Assigned: sefeng)
References
(Blocks 1 open bug)
Details
(Keywords: dev-doc-complete)
Attachments
(8 files)
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review |
https://wicg.github.io/scheduling-apis/#dom-scheduler-yield
I have a half baked patch, need to finish it.
Assignee | ||
Comment 1•6 months ago
|
||
Assignee | ||
Comment 2•6 months ago
|
||
Spec: https://wicg.github.io/scheduling-apis/#scheduling-state
This patch add the setup for WebTaskSchedulingState so that it
can be set and get in the following patch, by allowing it
to be carried over in continued Promise callbask and be set to
window globals and worker globals.
Assignee | ||
Comment 3•6 months ago
|
||
Assignee | ||
Comment 4•6 months ago
|
||
Updated•6 months ago
|
Updated•6 months ago
|
Updated•6 months ago
|
Updated•6 months ago
|
Assignee | ||
Comment 5•5 months ago
|
||
This is a missing step in the current implementation. When we about
to select a task, it should pick one from all scheduled tasks, including
the ones scheduled by different schedulers.
Assignee | ||
Updated•5 months ago
|
Assignee | ||
Comment 6•5 months ago
|
||
In Gecko, unlike other runnables where the TaskController
picks one each at a time, the TimeoutManager allows multiple
timers to run sequentially without allowing other runnables
to run in between.
This patch makes the user_blocking and user_visible tasks
dispatched by Scheduler API can run before timers.
Updated•5 months ago
|
Updated•5 months ago
|
Assignee | ||
Comment 7•5 months ago
|
||
Updated•5 months ago
|
Assignee | ||
Comment 8•5 months ago
|
||
Instead of passing a single AbortSignal
argument to CreateTask
,
we now separate it into a AbortSignal
and a TaskSignal
. They
could be the same when TaskController
is used, and if its
AbortController
, only AbortSignal
is non-null.
Comment 11•5 months ago
|
||
Backed out for causing hazard bustages @CycleCollectedJSContext.cpp.
Assignee | ||
Updated•4 months ago
|
Comment 13•4 months ago
|
||
Comment 14•4 months ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/912cf1adac80
https://hg.mozilla.org/mozilla-central/rev/78181c32bdc6
https://hg.mozilla.org/mozilla-central/rev/79b3b0148eb4
https://hg.mozilla.org/mozilla-central/rev/4b579a1c9b46
https://hg.mozilla.org/mozilla-central/rev/0773f669c498
https://hg.mozilla.org/mozilla-central/rev/4739af17e757
https://hg.mozilla.org/mozilla-central/rev/67bf260fe59b
https://hg.mozilla.org/mozilla-central/rev/2d0905a92f2c
Comment 15•4 months ago
|
||
Comment 16•4 months ago
|
||
Backed out for causing multiple failures.
- Backout link
- Push with failures
- Failure Log
- Failure line: /builds/worker/checkouts/gecko/dom/webscheduling/WebTaskScheduler.h:107:7: error: control reaches end of non-void function [-Werror=return-type]
Also, please check these wpt failures. It only fails on Windows 11 x64 24H2 opt and also fails in other forms, as it can be seen here.
Assignee | ||
Updated•4 months ago
|
Comment 18•3 months ago
|
||
Comment 19•3 months ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/cfae5efaae37
https://hg.mozilla.org/mozilla-central/rev/f441cb5e7e6e
https://hg.mozilla.org/mozilla-central/rev/bffd879a7547
https://hg.mozilla.org/mozilla-central/rev/2b4f7ebdb0b7
https://hg.mozilla.org/mozilla-central/rev/41d90165c19a
https://hg.mozilla.org/mozilla-central/rev/134228f242de
https://hg.mozilla.org/mozilla-central/rev/6934fa78ea13
https://hg.mozilla.org/mozilla-central/rev/00dc9f4af854
Updated•2 months ago
|
Comment 22•2 months ago
|
||
FF139 MDN docs work for this can be tracked in https://github.com/mdn/content/issues/39310. Mostly a browser compatibility data update and release note/experimental features doc update.
Description
•