[wpt-sync] Sync PR 43465 - Revert "Dispatch close event when MessagePort is disentangled"
Categories
(Core :: DOM: Core & HTML, task, P4)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox122 | --- | fixed |
People
(Reporter: wpt-sync, Unassigned)
References
()
Details
(Whiteboard: [wptsync downstream])
Sync web-platform-tests PR 43465 into mozilla-central (this bug is closed when the sync is complete).
PR: https://github.com/web-platform-tests/wpt/pull/43465
Details from upstream follow.
Hiroki Nakagawa <nhiroki@chromium.org> wrote:
Revert "Dispatch close event when MessagePort is disentangled"
This reverts commit 6a74d3d8049e1744b862757a73f90f3d7a5e08b0.
Reason for revert:
The tests newly added by the original CL are failing on
chrome_wpt_tests on the Linux Tests bot:
https://ci.chromium.org/ui/p/chromium/builders/ci/Linux%20Tests/138259/overviewOriginal change's description:
Dispatch close event when MessagePort is disentangled
We want to dispatch a close event when an entangled MessagePort is disconnected.
Given a pair of entangled ports, port1 and port2, if port2 is closed at any point,
a port1’s error handler is run.
So we can change an error handler to dispatch a close event.The tests of close event are as follows:
- port was explicitly closed.
- owning document was destroyed.
- owning document crashed.
- port was garbage collected.
Design Doc:https://docs.google.com/document/d/1lXZU2Pk2ycitqj8aL9kxT2aauwXqpA0vJDUalkXA29Y
Explainer:https://github.com/fergald/explainer-messageport-close
HTML spec PR:https://github.com/whatwg/html/pull/9933Bug: 1495616
Change-Id: I99f9f5a0d7cc63f0916da316ec666ba793215019
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5003089
Reviewed-by: Jeremy Roman \<jbroman@chromium.org>
Commit-Queue: Nonoka Muraki \<murakinonoka@chromium.org>
Reviewed-by: Ming-Ying Chung \<mych@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1231743}Bug: 1495616
Change-Id: Ib697597d6ab70a9a7bfc41a67dfc647698024a64
No-Presubmit: true
No-Tree-Checks: true
No-Try: trueReviewed-on: https://chromium-review.googlesource.com/5075742
WPT-Export-Revision: 1367e75dc145263824d6a3136457b2d123306a8a
| Assignee | ||
Comment 1•2 years ago
|
||
| Assignee | ||
Updated•2 years ago
|
| Assignee | ||
Comment 2•2 years ago
|
||
| Assignee | ||
Comment 3•2 years ago
|
||
CI Results
Ran 0 Firefox configurations based on mozilla-central, and Firefox, Chrome, and Safari on GitHub CI
Total 7 tests and 1 subtests
Status Summary
Firefox
OK : 5
PASS : 5
TIMEOUT: 4
Chrome
OK : 5
PASS : 4
FAIL : 1
TIMEOUT: 4
Safari
OK : 4
PASS : 2
FAIL : 2
TIMEOUT: 6
Links
Details
New Tests That Don't Pass
- /webmessaging/message-channels/close-event/close-event.tentative.any.worker.html [wpt.fyi]:
TIMEOUT(Chrome:TIMEOUT, Safari:TIMEOUT)- Close event listener added with onclose must be called.:
TIMEOUT(Chrome:TIMEOUT, Safari:TIMEOUT)
- Close event listener added with onclose must be called.:
- /webmessaging/message-channels/close-event/close-event.tentative.any.html [wpt.fyi]:
TIMEOUT(Chrome:TIMEOUT, Safari:TIMEOUT)- Close event listener added with onclose must be called.:
TIMEOUT(Chrome:TIMEOUT, Safari:TIMEOUT)
- Close event listener added with onclose must be called.:
Comment 6•2 years ago
|
||
| bugherder | ||
Description
•