Closed Bug 1531187 Opened 6 years ago Closed 6 years ago

[wpt-sync] Sync PR 15554 - [ElementTiming] Add request URL and responseEnd

Categories

(Testing :: web-platform-tests, enhancement, P4)

enhancement

Tracking

(firefox68 fixed)

RESOLVED FIXED
mozilla68
Tracking Status
firefox68 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

()

Details

(Whiteboard: [wptsync downstream])

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

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

Nicolás Peña Moreno <npm@chromium.org> wrote:

[ElementTiming] Add request URL and responseEnd

This CL adds the initial URL and the response end from ResourceTiming
into ElementTiming. The information is currently only stored on the
ResourceTimingInfo object which is not accessible to ImageElementTiming
(and in fact, could be gone by the time the ElementTiming code is
executed). Thus, we store the information in ImageResourceContent.

Bug: 879270
Change-Id: I72a80c67956adb6e869f39ca3c77829bad86044e
Reviewed-on: https://chromium-review.googlesource.com/1483733
WPT-Export-Revision: 68c9264cf3b9c3b9d3fdeacd817fc98191b85867

PR 15554 applied with additional changes from upstream: 679777df34300565db3d3dcca0f32424fb0472a0
Ran 13 tests and 14 subtests OK : 7 PASS : 4 FAIL : 4 TIMEOUT: 12 New tests that have failures or other problems: /element-timing/images-repeated-resource.html: TIMEOUT Element with elementtiming attribute is observable.: TIMEOUT /element-timing/observe-svg-image.html: TIMEOUT Able to observe svg image.: TIMEOUT
Pushed by james@hoppipolla.co.uk: https://hg.mozilla.org/integration/mozilla-inbound/rev/9e1e11e172bc [wpt PR 15554] - [ElementTiming] Add request URL and responseEnd, a=testonly https://hg.mozilla.org/integration/mozilla-inbound/rev/7e6f407b2e04 [wpt PR 15554] - Update wpt metadata, a=testonly
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla68
You need to log in before you can comment on or make changes to this bug.