Closed Bug 1564592 Opened 5 years ago Closed 5 years ago

[wpt-sync] Sync PR 17736 - [UserTimingL3] Throw TypeError on negative time stamp

Categories

(Core :: Performance, task, P4)

Product:
Core
Component:
Performance
Type:
task

Tracking

()

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

People

(Reporter: mozilla.org, Unassigned)

References

(
URL
)

Details

(Whiteboard: [wptsync downstream])

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

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

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

[UserTimingL3] Throw TypeError on negative time stamp

According to the spec (https://w3c.github.io/user-timing/):

  1. "If markOptions's startTime is negative, throw a TypeError.",
  2. "If mark is negative, throw a TypeError." when "Convert a mark to a timestamp"

The CL is to add these two checks accordingly.

Bug: 953865
Change-Id: I8475870cc883dc8c3d3d4f3e65a9d5a0a2189a58

Reviewed-on: https://chromium-review.googlesource.com/1691871
WPT-Export-Revision: f48c95313cd0cb1fb452126852babc5bc2a3e8a2

PR 17736 applied with additional changes from upstream: 27782199136cf350e2dd698856627821a60d712b
Component: web-platform-tests → Performance
Product: Testing → Core
Whiteboard: [wptsync downstream] → [wptsync downstream error]
PR 17736 applied with additional changes from upstream: 27782199136cf350e2dd698856627821a60d712b, 1f346b050d87656a040fa4fdf9f99567164e2a2b
Whiteboard: [wptsync downstream error] → [wptsync downstream]
PR 17736 applied with additional changes from upstream: 27782199136cf350e2dd698856627821a60d712b, 1f346b050d87656a040fa4fdf9f99567164e2a2b
Type: -- → task
Pushed by james@hoppipolla.co.uk:
https://hg.mozilla.org/integration/mozilla-inbound/rev/203009577895
[wpt PR 17736] - [UserTimingL3] Throw TypeError on negative time stamp, a=testonly

https://hg.mozilla.org/mozilla-central/rev/203009577895

Status: NEW → RESOLVED
Closed: 5 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.