Open
Bug 1347437
Opened 8 years ago
Updated 2 years ago
Promises should be run when JS stack is exhausted
Categories
(Core :: DOM: Core & HTML, defect, P3)
Core
DOM: Core & HTML
Tracking
()
NEW
| Tracking | Status | |
|---|---|---|
| firefox55 | --- | affected |
People
(Reporter: jwwang, Unassigned)
References
Details
Attachments
(1 file)
|
(deleted),
text/x-review-board-request
|
Details |
No description provided.
| Comment hidden (mozreview-request) |
|
Reporter | |
Comment 2•8 years ago
|
||
repro steps:
1. apply the patch
2. build
3. ./mach run dom/media/test/test_events.html
expected event sequence:
got preloadedmetadata event.
Promise resolved.
got loadedmetadata event.
actual event sequence:
got preloadedmetadata event.
got loadedmetadata event.
Promise resolved.
Micro tasks should be run between |r1->Run()| and |r2->Run()|.
Flags: needinfo?(bugs)
|
||
Comment 3•8 years ago
|
||
The .cpp code is very odd.
Microtasks should not run between those runs, _if_ there are no event listener which get called.
If event listeners are called
, then microtasks are called when outermost script execution ends, so usually at the end of each event listener.
Our Promises don't use microtasks. I'm still fixing that.
I guess this bug is about Promises, not microtasks.
Flags: needinfo?(bugs)
Summary: Micro tasks should be run when JS stack is exhausted → Promises should be run when JS stack is exhausted
|
||
Updated•8 years ago
|
Priority: -- → P3
|
Assignee | |
Updated•6 years ago
|
Component: DOM → DOM: Core & HTML
|
||
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•