Closed Bug 1712929 Opened 3 years ago Closed 3 years ago

[wpt-sync] Sync PR 29118 - [ResourceTiming] Update resource_connection_reuse{.https}.html

Categories

(Core :: Performance, task, P4)

task

Tracking

()

RESOLVED FIXED
91 Branch
Tracking Status
firefox91 --- fixed

People

(Reporter: mozilla.org, Unassigned)

References

()

Details

(Whiteboard: [wptsync downstream])

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

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

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

[ResourceTiming] Update resource_connection_reuse{.https}.html

This change updates the named test to conform to the new style we're
introducing to Resource Timing Web Platform Tests.

With this change, we're also expanding the contexts under which the test
will execute. Namely, this test will run under window, shared-worker and
dedicated-worker contexts.

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

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 15 tests and 5 subtests

Status Summary

Firefox

OK : 15
PASS : 32
FAIL : 11

Chrome

OK : 15
PASS : 36
FAIL : 7

Safari

OK : 14
PASS : 10
FAIL : 30
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)
/resource-timing/sizes-redirect-img.html
PerformanceResourceTiming sizes redirect image - direct URL: FAIL (Chrome: FAIL, Safari: FAIL)
PerformanceResourceTiming sizes redirect image - same origin redirect: FAIL (Chrome: FAIL, Safari: FAIL)
PerformanceResourceTiming sizes redirect image - cross origin redirect: FAIL (Chrome: FAIL, Safari: FAIL)
PerformanceResourceTiming sizes redirect image - cross origin to same origin redirect: FAIL (Chrome: FAIL, Safari: FAIL)
PerformanceResourceTiming sizes redirect image - same origin to remote origin to same origin redirect: FAIL (Chrome: FAIL, Safari: FAIL)

Pushed by wptsync@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/47f357e1f69c
[wpt PR 29118] - [ResourceTiming] Update resource_connection_reuse{.https}.html, a=testonly
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED
Target Milestone: --- → 91 Branch
You need to log in before you can comment on or make changes to this bug.