Closed Bug 1567279 Opened 5 years ago Closed 5 years ago

[wpt-sync] Sync PR 17909 - HTML: SharedArrayBuffer, cross-site, popups

Categories

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

task

Tracking

()

RESOLVED FIXED
mozilla70
Tracking Status
firefox70 --- fixed

People

(Reporter: mozilla.org, Unassigned)

References

()

Details

(Whiteboard: [wptsync downstream])

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

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

Anne van Kesteren <annevk@annevk.nl> wrote:

HTML: SharedArrayBuffer, cross-site, popups

This is not great, but then Firefox does not ship SAB yet. I guess we did not test this since we did not have cross-site domains back in the day.

Component: web-platform-tests → DOM: Core & HTML
Product: Testing → Core
PR 17909 applied with additional changes from upstream: b3418ad6bf7b49e59025e5278e1291587c6fc10e, 1da6bed5d8c4c38200383b86928b7be68bfb87da
PR 17909 applied with additional changes from upstream: b3418ad6bf7b49e59025e5278e1291587c6fc10e, 1da6bed5d8c4c38200383b86928b7be68bfb87da, dedb45f5f20e0ac884ac59634cceb8659cdcff7d
PR 17909 applied with additional changes from upstream: b3418ad6bf7b49e59025e5278e1291587c6fc10e, 1da6bed5d8c4c38200383b86928b7be68bfb87da, dedb45f5f20e0ac884ac59634cceb8659cdcff7d
Type: -- → task
Ran 1 tests and 1 subtests
TIMEOUT: 2

New tests that have failures or other problems:
/html/infrastructure/safe-passing-of-structured-data/shared-array-buffers/window-failure.https.html: TIMEOUT
    SharedArrayBuffer and a cross-site <iframe>: TIMEOUT
Pushed by wptsync@mozilla.com:
https://hg.mozilla.org/integration/mozilla-inbound/rev/0aa129ddd17c
[wpt PR 17909] - HTML: cross-site SharedArrayBuffer ought to not work, a=testonly
https://hg.mozilla.org/integration/mozilla-inbound/rev/69eb020a79bc
[wpt PR 17909] - Update wpt metadata, a=testonly
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla70
You need to log in before you can comment on or make changes to this bug.