Closed Bug 1552575 Opened 5 years ago Closed 5 years ago

[wpt-sync] Sync PR 16901 - [UserTimingL3] Throw error when global object is not Window object

Categories

(Core :: Performance, defect, P4)

defect

Tracking

()

RESOLVED FIXED
mozilla69
Tracking Status
firefox69 --- fixed

People

(Reporter: mozilla.org, Unassigned)

References

()

Details

(Whiteboard: [wptsync upstream])

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

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

Liquan(Max) Gu <maxlg@chromium.org> wrote:

[UserTimingL3] Throw error when global object is not Window object

The spec[1] says "If the global object is not a Window object, throw
a TypeError". We should check whether the global object is a window
object when converting a performance-timing name to timestamp. If
it is not, throw a Type Error.

[1] https://w3c.github.io/user-timing/#convert-a-name-to-a-timestamp

Bug: 953869
Change-Id: I188d810f2505a37f2cdfc823ce076cec96dd7839

Reviewed-on: https://chromium-review.googlesource.com/1613653
WPT-Export-Revision: 3448d9c58cbec4f38fc86e856ca3a958603db646

Component: web-platform-tests → Performance
Product: Testing → Core
Whiteboard: [wptsync downstream] → [wptsync downstream error]
Whiteboard: [wptsync downstream error] → [wptsync downstream]
Failed to get results from try push
Whiteboard: [wptsync downstream] → [wptsync downstream error]
Whiteboard: [wptsync downstream error] → [wptsync downstream]
Whiteboard: [wptsync downstream] → [wptsync downstream error]
Whiteboard: [wptsync downstream error] → [wptsync downstream]
Whiteboard: [wptsync downstream] → [wptsync downstream error]
Pushed by james@hoppipolla.co.uk:
https://hg.mozilla.org/integration/mozilla-inbound/rev/fbe5d20a501b
[wpt PR 16901] - [UserTimingL3] Throw error when global object is not Window object, a=testonly
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla69
Whiteboard: [wptsync downstream error] → [wptsync upstream]
You need to log in before you can comment on or make changes to this bug.