Closed
Bug 1958943
Opened 3 months ago
Closed 3 months ago
Re-enable dom.enable_web_task_scheduling in Nightly
Categories
(Core :: DOM: Core & HTML, task)
Core
DOM: Core & HTML
Tracking
()
RESOLVED
FIXED
139 Branch
| Tracking | Status | |
|---|---|---|
| firefox139 | --- | fixed |
People
(Reporter: sefeng, Assigned: sefeng)
References
Details
(Keywords: dev-doc-complete)
Attachments
(1 file)
No description provided.
|
Assignee | |
Comment 1•3 months ago
|
||
Pushed by sefeng@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/c52b12a54378
Re-enable dom.enable_web_task_scheduling r=smaug
Status: NEW → RESOLVED
Closed: 3 months ago
status-firefox139:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 139 Branch
Keywords: dev-doc-needed
|
||
Updated•3 months ago
|
Summary: Re-enable dom.enable_web_task_scheduling → Re-enable dom.enable_web_task_scheduling in Nightly
|
||
Updated•2 months ago
|
QA Whiteboard: [qa-triage-done-c140/b139]
|
||
Comment 4•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.
Keywords: dev-doc-needed → dev-doc-complete
|
|
||
Comment 5•2 months ago
|
||
Looks like this API is complete to-spec except for the TaskSignal.any() static method. Is there an intent to add that before this ships?
Flags: needinfo?(sefeng)
|
|
Assignee | |
Comment 6•2 months ago
|
||
I missed that totally, thanks for pointing it out!
I just filed bug 1964407 for that. I think we should get it implement before shipping this and it should be easy to implement given we have AbortSignal.any already
Flags: needinfo?(sefeng)
You need to log in
before you can comment on or make changes to this bug.
Description
•