Closed Bug 1652767 Opened 5 years ago Closed 3 months ago

New wpt failures in /webmessaging/multi-globals/ [broadcastchannel-incumbent.sub.html, broadcastchannel-current.sub.html]

Categories

(Core :: DOM: postMessage, defect, P3)

defect

Tracking

()

RESOLVED DUPLICATE of bug 1652421

People

(Reporter: wpt-sync, Unassigned)

References

Details

(Keywords: parity-chrome, parity-safari, Whiteboard: [wpt,dom-lws-bugdash-triage])

Syncing wpt PR 24568 found new untriaged test failures in CI

Tests Affected

Firefox-only failures

/webmessaging/multi-globals/broadcastchannel-incumbent.sub.html: TIMEOUT

New Tests That Don't Pass

/webmessaging/multi-globals/broadcastchannel-incumbent.sub.html
The incumbent page being cross-origin must not prevent the BroadcastChannel message from being seen: TIMEOUT (Chrome: PASS, Safari: FAIL)
/webmessaging/multi-globals/broadcastchannel-current.sub.html
The current page being cross-origin must prevent the BroadcastChannel message from being seen: FAIL (Chrome: PASS, Safari: FAIL)

CI Results

Gecko CI (Treeherder)
GitHub PR Head

Notes

These updates will be on mozilla-central once bug 1652172 lands.

Note: this bug is for tracking fixing the issues and is not
owned by the wpt sync bot.

This bug is linked to the relevant tests by an annotation in
https://github.com/web-platform-tests/wpt-metadata. These annotations
can be edited using the wpt interop dashboard
https://jgraham.github.io/wptdash/

If this bug is split into multiple bugs, please also update the
annotations, otherwise we are unable to track which wpt issues are
already triaged. Resolving as duplicate or closing this issue should
be cause the bot to automatically update or remove the annotation.

Component: DOM: Core & HTML → DOM: postMessage
Severity: -- → S3
Priority: -- → P3
Whiteboard: [wpt] → [wpt,dom-lws-bugdash-triage]

we're passing now.

Status: NEW → RESOLVED
Closed: 3 months ago
Resolution: --- → WORKSFORME

Fixed in bug 1652421.

Duplicate of bug: 1652421
Resolution: WORKSFORME → DUPLICATE
You need to log in before you can comment on or make changes to this bug.