Closed Bug 1710430 Opened 3 years ago Closed 3 years ago

[wpt-sync] Sync PR 28939 - Cleanup resource_timing_TAO_match_origin test

Categories

(Core :: Performance, task, P4)

Product:
Core
Component:
Performance
Type:
task

Tracking

()

Status:
RESOLVED FIXED
Milestone:
90 Branch
Tracking Flags:
Tracking Status
firefox90 --- fixed

People

(Reporter: mozilla.org, Unassigned)

References

(
URL
)

Details

(Whiteboard: [wptsync downstream])

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

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

b'Nicol\xc3\xa1s Pe\xc3\xb1a Moreno <npm@chromium.org>' wrote:

Cleanup resource_timing_TAO_match_origin test

Bug: 1171767
Change-Id: I25c2a16be5e7094aa4cc46ef4be3b31e80d1b412
Reviewed-on: https://chromium-review.googlesource.com/2879876
WPT-Export-Revision: 3ecec55c8a024235c5db0a9b3f6601a52de64f6f

Component: web-platform-tests → Performance
Product: Testing → Core

CI Results

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

Total 12 tests and 1 subtests

Status Summary

Firefox

OK : 12
PASS : 18
FAIL : 6

Chrome

OK : 12
PASS : 22
FAIL : 2

Safari

OK : 11
PASS : 11
FAIL : 10
TIMEOUT: 2
NOTRUN : 2

Links

Gecko CI (Treeherder)
GitHub PR Head
GitHub PR Base

Details

New Tests That Don't Pass

/resource-timing/SO-XO-SO-redirect-chain-tao.https.html
Verify that cross origin resources' timings are not exposed when same-origin=>cross-origin=>same-origin redirects have no Timing-Allow-Origin: headers.: FAIL (Chrome: PASS, Safari: FAIL)
Verify that cross origin resources' timings are not exposed when same-origin=>cross-origin=>same-origin redirects have Timing-Allow-Origin: headers only on some of the responses.: FAIL (Chrome: PASS, Safari: FAIL)
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/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/nextHopProtocol-is-tao-protected.https.html
Add TAO-less iframe from remote origin. Make sure nextHopProtocol is the empty string: FAIL (Chrome: PASS, 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)

Pushed by wptsync@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/69d636267a62
[wpt PR 28939] - Cleanup resource_timing_TAO_match_origin test, a=testonly

https://hg.mozilla.org/mozilla-central/rev/69d636267a62

Status: NEW → RESOLVED
Closed: 3 years ago
status-firefox90: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 90 Branch
You need to log in before you can comment on or make changes to this bug.