Closed
Bug 1517886
Opened 5 years ago
Closed 5 years ago
[wpt-sync] Sync PR 14724 - [Resource-Timing] Fix non-zero secureConnectionStart in cleartext http
Categories
(Core :: DOM: Core & HTML, enhancement, P4)
Core
DOM: Core & HTML
Tracking
()
RESOLVED
FIXED
mozilla67
Tracking | Status | |
---|---|---|
firefox67 | --- | fixed |
People
(Reporter: mozilla.org, Unassigned)
References
()
Details
(Whiteboard: [wptsync downstream])
Sync web-platform-tests PR 14724 into mozilla-central (this bug is closed when the sync is complete). PR: https://github.com/web-platform-tests/wpt/pull/14724 Details from upstream follow. Yoav Weiss <yoavweiss@chromium.org> wrote: > [Resource-Timing] Fix non-zero secureConnectionStart in cleartext http > > It seems we introduced[1] an issue inte secureConnectionStart values > where we wrongfully expose the fetchStart value there in cases where the > connection is not secure. > I'm fixing the spec[2], as it was a literal implementation of the "on > getting" processing there. This CL fixes our implementation. > > [1] https://chromium-review.googlesource.com/c/chromium/src/+/1363906 > [2] https://github.com/w3c/resource-timing/pull/194 > > Change-Id: Ib5e74ff70eddb0a96506e8955c5df2b01cc3d73a > > Reviewed-on: https://chromium-review.googlesource.com/1396129 > WPT-Export-Revision: 46582159436b3ecf3eef01ce0cb42f7ed331cf17
Assignee | ||
Updated•5 years ago
|
Component: web-platform-tests → DOM
Product: Testing → Core
Assignee | ||
Comment 1•5 years ago
|
||
Pushed to try https://treeherder.mozilla.org/#/jobs?repo=try&revision=ea718c23be95df18410d00fa1026dd7975d70703
Assignee | ||
Comment 2•5 years ago
|
||
Pushed to try (stability) https://treeherder.mozilla.org/#/jobs?repo=try&revision=b05ee71a71259ee23defd42e488b1791564816e6
Assignee | ||
Comment 3•5 years ago
|
||
Pushed to try https://treeherder.mozilla.org/#/jobs?repo=try&revision=5c852a4f4cdb9228391925ed1922693f5a31d5f4
Assignee | ||
Comment 4•5 years ago
|
||
Pushed to try (stability) https://treeherder.mozilla.org/#/jobs?repo=try&revision=943c161e9822c289faa13c2eb12b92bd61f9ef4a
Assignee | ||
Comment 5•5 years ago
|
||
Pushed to try https://treeherder.mozilla.org/#/jobs?repo=try&revision=8048edf52f0ea2720ecc4db6a25fe38bf217f6b8
Assignee | ||
Updated•5 years ago
|
Whiteboard: [wptsync downstream] → [wptsync downstream error]
Assignee | ||
Updated•5 years ago
|
Whiteboard: [wptsync downstream error] → [wptsync downstream]
Assignee | ||
Comment 6•5 years ago
|
||
Pushed to try (stability) https://treeherder.mozilla.org/#/jobs?repo=try&revision=53f6dd2a390acb092c0c058a9092cca6c7e3e54a
Assignee | ||
Comment 7•5 years ago
|
||
Ran 2 tests and 8 subtests OK : 1 PASS : 3 FAIL : 5 New tests that have failures or other problems: /resource-timing/resource_connection_reuse.https.html connectEnd and fetchStart should be the same: FAIL connectStart and fetchStart should be the same: FAIL domainLookupEnd and fetchStart should be the same: FAIL domainLookupStart and fetchStart should be the same: FAIL secureConnectStart and fetchStart should be the same: FAIL Tests that are disabled for instability: /resource-timing/resource_connection_reuse.html
Pushed by james@hoppipolla.co.uk: https://hg.mozilla.org/integration/mozilla-inbound/rev/049104c8c153 [wpt PR 14724] - [Resource-Timing] Fix non-zero secureConnectionStart in cleartext http, a=testonly https://hg.mozilla.org/integration/mozilla-inbound/rev/12b57b944376 [wpt PR 14724] - Update wpt metadata, a=testonly
Pushed by james@hoppipolla.co.uk: https://hg.mozilla.org/integration/mozilla-inbound/rev/305d1c08372b [wpt PR 14724] - [Resource-Timing] Fix non-zero secureConnectionStart in cleartext http, a=testonly https://hg.mozilla.org/integration/mozilla-inbound/rev/14c727acec10 [wpt PR 14724] - Update wpt metadata, a=testonly
Comment 10•5 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/305d1c08372b
https://hg.mozilla.org/mozilla-central/rev/14c727acec10
Status: NEW → RESOLVED
Closed: 5 years ago
status-firefox67:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla67
Updated•5 years ago
|
Component: DOM → DOM: Core & HTML
You need to log in
before you can comment on or make changes to this bug.
Description
•