Closed Bug 1468897 Opened 7 years ago Closed 7 years ago

[wpt-sync] Sync PR 11515 - Use Referrer Policy IDL as dependency for fetch

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: wpt-sync, Unassigned)

References

(
URL
)

Details

(Whiteboard: [wptsync upstream])

Sync web-platform-tests PR 11515 into mozilla-central (this bug is closed when the sync is complete). PR: https://github.com/web-platform-tests/wpt/pull/11515 Details from upstream follow. Chris Nardi <christopherncarmel@hotmail.com> wrote: > Use Referrer Policy IDL as dependency for fetch > > In newer versions of webidl2.js, empty enums are not allowed. We can easily switch to using the actual definition in the Referrer Policy spec to avoid running into any problems when upgrading webidl2.js. > > This change leads to the same number of passing/failing tests on Chrome.
Component: web-platform-tests → DOM
Product: Testing → Core
Ran 4 tests and 3 subtests OK : 3 FAIL : 3 TIMEOUT: 1 Existing tests that now have a worse result (e.g. they used to PASS and now FAIL): /fetch/api/idl.any.html Fetch Standard IDL: FAIL /fetch/api/idl.any.sharedworker.html Fetch Standard IDL: FAIL /fetch/api/idl.any.worker.html Fetch Standard IDL: FAIL
Pushed by james@hoppipolla.co.uk: https://hg.mozilla.org/integration/mozilla-inbound/rev/25e29cb96289 [wpt PR 11515] - Use Referrer Policy IDL as dependency for fetch, a=testonly https://hg.mozilla.org/integration/mozilla-inbound/rev/f4f4a5e0ccd1 [wpt PR 11515] - Update wpt metadata, a=testonly
Whiteboard: [wptsync downstream] → [wptsync upstream]
https://hg.mozilla.org/mozilla-central/rev/25e29cb96289 https://hg.mozilla.org/mozilla-central/rev/f4f4a5e0ccd1
Status: NEW → RESOLVED
Closed: 7 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.