Closed Bug 1700347 Opened 5 years ago Closed 5 years ago

[wpt-sync] Sync PR 28188 - [ResourceTiming]: Update resource_timing_cross_origin_redirect_chain.html

Categories

(Core :: Performance: General, task, P4)

task

Tracking

()

RESOLVED FIXED
90 Branch
Tracking Status
firefox90 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

()

Details

(Whiteboard: [wptsync downstream])

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

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

b'Tom McKee <tommckee@chromium.org>' wrote:

[ResourceTiming]: Update resource_timing_cross_origin_redirect_chain.html

This change updates and renames the above file to match the new style
and structure being introduced for the linked bug. In particular, this
test was checking an odd corner case where a cross-origin redirect
points to a same-origin resource but this was unapparent from the
original name.

Bug: 1171767
Change-Id: If3118a6a7333ec8520e36d8e8ae28bcbf0d20b9d
GithubIssue: https://github.com/w3c/resource-timing/issues/254
Reviewed-on: https://chromium-review.googlesource.com/2774029
WPT-Export-Revision: ad113c6807a998c8f54cd028978e2b43ed6a235e

PR 28188 applied with additional changes from upstream: 50e1824bd054ff1f659969b7390fb32d631590d6
Component: web-platform-tests → Performance
Product: Testing → Core

CI Results

Ran 0 Firefox configurations based on mozilla-central, and Firefox, Chrome, and Safari on GitHub CI

Total 8 tests and 1 subtests

Status Summary

Firefox

OK : 8
PASS : 11
FAIL : 4

Chrome

OK : 8
PASS : 13
FAIL : 2

Safari

OK : 6
PASS : 6
FAIL : 5
TIMEOUT: 4
NOTRUN : 2

Links

GitHub PR Head
GitHub PR Base

Details

New Tests That Don't Pass

/resource-timing/cross-origin-start-end-time-with-redirects.html
Verify that cross-origin resources don't implicitly expose their redirect timings: FAIL (Chrome: FAIL, Safari: FAIL)
/resource-timing/same-origin-from-cross-origin-redirect.html
Verify that cross origin resources' timings are exposed when the final resource at the end of an HTTP redirect chain is same-origin.: FAIL (Chrome: PASS, Safari: FAIL)
/resource-timing/tao-origin-SO-XO-SO-redirect-chain.https.html
Verify that cross origin resources' timings are not exposed when same-origin=>cross-origin=>same-origin redirects have Timing-Allow-Origin: headers with a specific origin.: FAIL (Chrome: FAIL, Safari: FAIL)
/resource-timing/tao-star-SO-XO-SO-redirect-chain.https.html
Verify that cross origin resources' timings are exposed when cross-origin redirects have Timing-Allow-Origin: * headers: FAIL (Chrome: PASS, Safari: TIMEOUT)

Pushed by wptsync@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/56386b444f9c [wpt PR 28188] - [ResourceTiming]: Update resource_timing_cross_origin_redirect_chain.html, a=testonly https://hg.mozilla.org/integration/autoland/rev/09e60a815c58 [wpt PR 28188] - Update wpt metadata, a=testonly
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → 90 Branch
You need to log in before you can comment on or make changes to this bug.