[wpt-sync] Sync PR 14548 - Verify TTFB in resource-timing.html WPT by measuring that the delay occurs between responseStart and responseEnd

RESOLVED FIXED in Firefox 66

Status

()

enhancement
P4
normal
RESOLVED FIXED
8 months ago
5 months ago

People

(Reporter: wptsync, Unassigned)

Tracking

unspecified
mozilla66
Points:
---

Firefox Tracking Flags

(firefox66 fixed)

Details

(Whiteboard: [wptsync downstream], )

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

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

Andrew Comminos <acomminos@fb.com> wrote:
>  Verify TTFB in resource-timing.html WPT by measuring that the delay occurs between responseStart and responseEnd
>  
>  When simulating a delay after a statusline, measure that the delay is
>  not included in the TTFB by measuring that it occurred between
>  responseStart and responseEnd rather than requestStart and
>  responseStart. This makes the tests less flaky when subject to shaky
>  network and thread scheduling conditions, as might be present using
>  Firefox's chaos mode.
>  
>  Bug: 568024
>  Change-Id: I0356f6256af6bc87fbb14860ed05472526c03e5d
>  Reviewed-on: https://chromium-review.googlesource.com/c/1377725
>  Reviewed-by: Yoav Weiss \<yoav@yoav.ws>
>  Commit-Queue: Andrew Comminos \<acomminos@fb.com>
>  Cr-Commit-Position: refs/heads/master@{#617021}
>
PR 14548 applied with additional changes from upstream: 6d3120bad3e5d55bfebb3063a5ef04e7fc231905
Component: web-platform-tests → DOM
Product: Testing → Core
Ran 1 tests


Tests that are disabled for instability:
/resource-timing/resource-timing.html
Pushed by james@hoppipolla.co.uk:
https://hg.mozilla.org/integration/mozilla-inbound/rev/7b3a9d543fa3
[wpt PR 14548] - Verify TTFB in resource-timing.html WPT by measuring that the delay occurs between responseStart and responseEnd, a=testonly
Status: NEW → RESOLVED
Closed: 7 months ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla66
Component: DOM → DOM: Core & HTML
You need to log in before you can comment on or make changes to this bug.