Closed Bug 1467848 Opened 6 years ago Closed 6 years ago

[wpt-sync] Sync PR 11428 - Fetch: test Cross-Origin-Resource-Policy: same-site's scheme restriction

Categories

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

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

Tracking

()

Status:
RESOLVED FIXED
Milestone:
mozilla63
Tracking Flags:
Tracking Status
firefox63 --- fixed

People

(Reporter: mozilla.org, Unassigned)

References

(
URL
)

Details

(Whiteboard: [wptsync downstream]) 

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

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

Anne van Kesteren <annevk@annevk.nl> wrote:
>  Fetch: test Cross-Origin-Resource-Policy: same-site's scheme restriction
>  
>  Supplements #11171.
>  
>  For https://github.com/whatwg/fetch/pull/733.
Component: web-platform-tests → DOM
Product: Testing → Core
PR 11428 applied with additional changes from upstream: 53f7340307c1c0fa4ab96e79d88c69a7870030f4
Ran 3 tests and 3 subtests
OK     : 3
PASS   : 1
FAIL   : 2

New tests that have failures or other problems:
/fetch/cross-origin-resource-policy/scheme-restriction.any.html
    Cross-Origin-Resource-Policy: same-site's scheme restriction: FAIL
/fetch/cross-origin-resource-policy/scheme-restriction.any.worker.html
    Cross-Origin-Resource-Policy: same-site's scheme restriction: FAIL
Pushed by james@hoppipolla.co.uk:
https://hg.mozilla.org/integration/mozilla-inbound/rev/2088a3b878a4
[wpt PR 11428] - Fetch: test Cross-Origin-Resource-Policy: same-site's scheme restriction, a=testonly
https://hg.mozilla.org/integration/mozilla-inbound/rev/4b469f7e2be3
[wpt PR 11428] - Update wpt metadata, a=testonly
https://hg.mozilla.org/mozilla-central/rev/2088a3b878a4
https://hg.mozilla.org/mozilla-central/rev/4b469f7e2be3
Status: NEW → RESOLVED
Closed: 6 years ago
status-firefox63: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla63
Component: DOM → DOM: Core & HTML
You need to log in before you can comment on or make changes to this bug.