Measure usage of performance.measure without a second parameter in a worker |
||
Issue descriptionThe current behavior doesn't match the spec. If usage is low enough, we'd like to just throw in this case.
,
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?
,
Jan 3 2018
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 |
||
Comment 1 by npm@chromium.org
, Jan 2 2018