[wpt-sync] Sync PR 32756 - [scheduling APIs] Remove scheduler.currentTaskSignal prototype
Categories
(Testing :: web-platform-tests, task, P4)
Tracking
(firefox99 fixed)
| Tracking | Status | |
|---|---|---|
| firefox99 | --- | fixed |
People
(Reporter: mozilla.org, Unassigned)
References
(Depends on 1 open bug, )
Details
(Whiteboard: [wptsync downstream])
Sync web-platform-tests PR 32756 into mozilla-central (this bug is closed when the sync is complete).
PR: https://github.com/web-platform-tests/wpt/pull/32756
Details from upstream follow.
Scott Haseley <shaseley@chromium.org> wrote:
[scheduling APIs] Remove scheduler.currentTaskSignal prototype
Removing this to make room for task attribution tracking
(crrev.com/c/3310850), which also needs the V8 APIs to get/set
continuation preserved embedder data. Since we don't know if we want to
pursue shipping this in its current form, we'll make room for the task
attribuion code rather than change the V8 API to handle multiple values.Removing this API also removes the creation of implicit task signals,
which involved some slight refactoring. In particular, DOMTaskQueue is
modified to hold the priority (used in DOMTask for tracing and metrics)
and DOMTask is modified to take a potentially null AbortSignal and
non-null DOMTaskQueue instead of a non-null TaskSignal (potentially
implicit) and a task runner.Bug: 995862, 1291129
Change-Id: I103e520f1e7d1f236a4845f099f0d0a662d1c017
Reviewed-on: https://chromium-review.googlesource.com/3449072
WPT-Export-Revision: 7be890733b48310b17668000f3777182e99c85d7
|
Assignee | |
Comment 1•3 years ago
|
||
|
|
Assignee | |
Comment 2•3 years ago
|
||
|
|
Assignee | |
Comment 4•3 years ago
|
||
|
|
Assignee | |
Comment 6•3 years ago
|
||
|
||
Comment 7•3 years ago
|
||
| bugherder | ||
Description
•