New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 796600 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Jan 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Task



Sign in to add a comment

Measure usage of performance.measure without a second parameter in a worker

Project Member Reported by tdres...@chromium.org, Dec 20 2017

Issue description

The current behavior doesn't match the spec. If usage is low enough, we'd like to just throw in this case.
 

Comment 1 by npm@chromium.org, Jan 2 2018

Can you clarify this a little bit? What is wrong about the current behavior? This method is implemented the same way for worker and window, is it broken for window too? And what do you mean by 'just throw in'?

Comment 2 by npm@chromium.org, Jan 2 2018

Oh if this is related to https://github.com/w3c/user-timing/issues/22 then I think that our implementation is on par with level 2 so the behavior matches the spec. And then we don't really need to measure the usage requested?
Status: WontFix (was: Assigned)
If usage is low enough, we'd like to throw an exception in this case.

Yeah, looks like Philip came to the same conclusion that this is fine.
Closing.

Sign in to add a comment