Closed
Bug 2033915
Opened 6 months ago
Closed 5 months ago
Add off by default support for exposing safe resolve semantics as a second parameter to the resolve function of a promise.
Categories
(Core :: JavaScript Engine, task, P3)
Core
JavaScript Engine
Tracking
()
RESOLVED
FIXED
153 Branch
| Tracking | Status | |
|---|---|---|
| firefox153 | --- | fixed |
People
(Reporter: mgaudet, Assigned: mgaudet)
References
(Blocks 1 open bug)
Details
Attachments
(1 external file)
This would make the resolve function (from new Promise((resolve, _) ) take a second boolen parameter which opts resolution into Safe Resolve semantics as specified in the Thenable Curtailment proposal.
|
Assignee | |
Updated•6 months ago
|
Severity: -- → N/A
Priority: -- → P3
|
|
Assignee | |
Comment 1•6 months ago
|
||
|
||
Updated•6 months ago
|
Assignee: nobody → mgaudet
Attachment #9584715 -
Attachment description: WIP: Bug 2033915 - Add off-by-defualt support for exposing safe-resolve semantics to user code → Bug 2033915 - Add off-by-default support for exposing safe-resolve semantics to user code r?dminor
Status: NEW → ASSIGNED
|
|
Assignee | |
Updated•6 months ago
|
Summary: Add off by defualt support for exposing safe resolve semantics as a second parameter to the resolve function of a promise. → Add off by default support for exposing safe resolve semantics as a second parameter to the resolve function of a promise.
Pushed by mgaudet@mozilla.com:
https://github.com/mozilla-firefox/firefox/commit/4f21d3090235
https://hg.mozilla.org/integration/autoland/rev/58835f42c2eb
Add off-by-default support for exposing safe-resolve semantics to user code r=dminor
|
||
Comment 3•5 months ago
|
||
| bugherder | ||
Status: ASSIGNED → RESOLVED
Closed: 5 months ago
status-firefox153:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 153 Branch
|
||
Updated•5 months ago
|
QA Whiteboard: [qa-triage-done-c154/b153]
You need to log in
before you can comment on or make changes to this bug.
Description
•