Closed Bug 1581220 Opened 6 years ago Closed 6 years ago

[wpt-sync] Sync PR 19053 - [resource-timing] Align TAO processing with CORS

Categories

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

Product:
Core
Component:
Performance: General
Type:
task

Tracking

()

Status:
RESOLVED FIXED
Milestone:
mozilla71
Tracking Flags:
Tracking Status
firefox71 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

(
URL
)

Details

(Whiteboard: [wptsync downstream])

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

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

Yoav Weiss <yoavweiss@chromium.org> wrote:

[resource-timing] Align TAO processing with CORS

Change-Id: I4c77ba5dbbe22c3de4dd05e4c7a8ac2c1526603b
Reviewed-on: https://chromium-review.googlesource.com/1803916
WPT-Export-Revision: 9c76a9fb8ea6090be7c5d2b363d3030278d12d6a

Component: web-platform-tests → Performance
Product: Testing → Core
Ran 5 tests and 35 subtests OK : 5 PASS : 30 FAIL : 5 New tests that have failures or other problems: /resource-timing/crossorigin-sandwich-partial-TAO.sub.html redirectEnd == 0 in cross-origin redirect with Timing-Allow-Origin in some of the chain but not all of it.: FAIL redirectStart == 0 in cross-origin redirect with Timing-Allow-Origin in some of the chain but not all of it.: FAIL startTime == fetchStart in cross-origin redirect with Timing-Allow-Origin in some of the chain but not all of it.: FAIL
Pushed by wptsync@mozilla.com: https://hg.mozilla.org/integration/mozilla-inbound/rev/88ab455879f4 [wpt PR 19053] - [resource-timing] Align TAO processing with CORS, a=testonly https://hg.mozilla.org/integration/mozilla-inbound/rev/3506fb6955b8 [wpt PR 19053] - Update wpt metadata, a=testonly

https://hg.mozilla.org/mozilla-central/rev/88ab455879f4
https://hg.mozilla.org/mozilla-central/rev/3506fb6955b8

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