Closed Bug 1517226 Opened 6 years ago Closed 6 years ago

[wpt-sync] Sync PR 9307 - Test that resources fetched by cross-origin CSS are not in the timeline

Categories

(Testing :: web-platform-tests, enhancement, P4)

enhancement

Tracking

(firefox67 fixed)

RESOLVED FIXED
mozilla67
Tracking Status
firefox67 --- fixed

People

(Reporter: mozilla.org, Unassigned)

References

()

Details

(Whiteboard: [wptsync downstream])

Sync web-platform-tests PR 9307 into mozilla-central (this bug is closed when the sync is complete). PR: https://github.com/web-platform-tests/wpt/pull/9307 Details from upstream follow. Yoav Weiss <yoav@yoav.ws> wrote: > Test that resources fetched by cross-origin CSS are not in the timeline > > Closes https://github.com/w3c/resource-timing/issues/70 > > This is a long standing missing test. Seems like all browsers are doing the wrong thing here, which leads me to think we may need to change the spec... > > >
Whiteboard: [wptsync downstream] → [wptsync downstream error]
Whiteboard: [wptsync downstream error] → [wptsync downstream]
Ran 1 tests and 1 subtests OK : 1 FAIL : 1 New tests that have failures or other problems: /resource-timing/no-entries-for-cross-origin-css-fetched.sub.html Make sure that resources fetched by cross origin CSS are not in the timeline.: FAIL
Pushed by james@hoppipolla.co.uk: https://hg.mozilla.org/integration/mozilla-inbound/rev/817da0778b4a [wpt PR 9307] - Test that resources fetched by cross-origin CSS are not in the timeline, a=testonly https://hg.mozilla.org/integration/mozilla-inbound/rev/09d637fe3c30 [wpt PR 9307] - Update wpt metadata, a=testonly
Pushed by james@hoppipolla.co.uk: https://hg.mozilla.org/integration/mozilla-inbound/rev/b69c78d6d75e [wpt PR 9307] - Test that resources fetched by cross-origin CSS are not in the timeline, a=testonly https://hg.mozilla.org/integration/mozilla-inbound/rev/f1bb4858b2ac [wpt PR 9307] - Update wpt metadata, a=testonly
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla67
You need to log in before you can comment on or make changes to this bug.