Closed
Bug 1766260
Opened 2 years ago
Closed 2 years ago
A transferred MessagePort is slower than setTimeout(0)
Categories
(Core :: DOM: postMessage, defect)
Core
DOM: postMessage
Tracking
()
RESOLVED
INVALID
People
(Reporter: saschanaz, Unassigned)
References
Details
Attachments
(1 file, 1 obsolete file)
1.16 KB,
text/html
|
Details |
This is probably the core issue behind the failing tests in streams/transferable
.
Gecko fails to pass the second assert_true
in the attached test, while Chrome passes both.
Reporter | ||
Comment 1•2 years ago
|
||
Reporter | ||
Comment 2•2 years ago
|
||
Raw HTML version of the same test.
Reporter | ||
Comment 3•2 years ago
|
||
Hi Olli, this is my minimal test case for the issue we talked earlier (https://phabricator.services.mozilla.com/D139525?id=568935#inline-795931), do you have any idea?
Flags: needinfo?(bugs)
Reporter | ||
Comment 4•2 years ago
|
||
Per :nika and :asuth the spec specifies that the MessagePort behavior changes after transfer: https://html.spec.whatwg.org/multipage/web-messaging.html#unshipped-port-message-queue (where the has been shipped
flag changes after transfer). I'll fix the streams/transferable tests based on this.
Flags: needinfo?(bugs)
Reporter | ||
Updated•2 years ago
|
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → INVALID
Updated•2 years ago
|
Attachment #9273656 -
Attachment is obsolete: true
You need to log in
before you can comment on or make changes to this bug.
Description
•