Closed Bug 1566462 Opened 6 years ago Closed 6 years ago

[wpt-sync] Sync PR 17852 - Rename render timestamp in ElementTiming and LargestContentfulPaint

Categories

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

Product:
Testing
Component:
web-platform-tests
Type:
task

Tracking

(firefox70 fixed)

Status:
RESOLVED FIXED
Milestone:
mozilla70
Tracking Flags:
Tracking Status
firefox70 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

(
URL
)

Details

(Whiteboard: [wptsync downstream error])

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

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

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

Rename render timestamp in ElementTiming and LargestContentfulPaint

Currently, the rendering timestamp is exposed in startTime. This may not
be ideal because analytics providers may be using certain default
filters which could sort by startTime, but the timestamp is 0 for cross
origin images. Also, 'renderTime' is more indicative of the timestamp
being exposed.

Bug: 879270, 942033, 965505
Change-Id: Iee283426173facd1e67343fd376e344517540423
Reviewed-on: https://chromium-review.googlesource.com/1703480
WPT-Export-Revision: 4903078387f09e7ea15c97a697192bef4160238b

Whiteboard: [wptsync downstream] → [wptsync downstream error]
Type: -- → task
Pushed by james@hoppipolla.co.uk: https://hg.mozilla.org/integration/mozilla-inbound/rev/831f05e13802 [wpt PR 17852] - Rename render timestamp in ElementTiming and LargestContentfulPaint, a=testonly

https://hg.mozilla.org/mozilla-central/rev/831f05e13802

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