Closed Bug 1762667 Opened 2 years ago Closed 2 years ago

[wpt-sync] Sync PR 33479 - Close a MessagePort if it is created in a destroyed context.

Categories

(Core :: DOM: Core & HTML, task, P4)

Product:
Core
Component:
DOM: Core & HTML
Type:
task

Tracking

()

Status:
RESOLVED FIXED
Milestone:
101 Branch
Tracking Flags:
Tracking Status
firefox101 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

(
URL
)

Details

(Whiteboard: [wptsync downstream])

Sync web-platform-tests PR 33479 into mozilla-central (this bug is closed when the sync is complete).

PR: https://github.com/web-platform-tests/wpt/pull/33479
Details from upstream follow.

Marijn Kruisselbrink <mek@chromium.org> wrote:

Close a MessagePort if it is created in a destroyed context.

MessagePort assumes it is only destroyed either after ContextDestroyed,
or after the port has been closed explicitly. As it turns out ports that
were created in an already detached iframe would violate this invariant,
causing issues.

Bug: 1228661
Change-Id: Ib1abce15f1d1d15f044de19fe0534767db488af0
Reviewed-on: https://chromium-review.googlesource.com/3561845
WPT-Export-Revision: 5303f9517eae0e97f9d5d39f8a90f3bd622f5e58

Component: web-platform-tests → DOM: Core & HTML
Product: Testing → Core

CI Results

Ran 0 Firefox configurations based on mozilla-central, and Firefox, Chrome, and Safari on GitHub CI

Total 1 tests and 2 subtests

Status Summary

Firefox

OK : 1
PASS: 2

Chrome

OK : 1
PASS: 2

Safari

OK : 1
PASS: 2

Links

GitHub PR Head
GitHub PR Base

Pushed by wptsync@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/3db032ff3414
[wpt PR 33479] - Close a MessagePort if it is created in a destroyed context., a=testonly

https://hg.mozilla.org/mozilla-central/rev/3db032ff3414

Status: NEW → RESOLVED
Closed: 2 years ago
status-firefox101: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 101 Branch
You need to log in before you can comment on or make changes to this bug.