Bug 165503

Summary: performance.now() should truncate to 100us
Product: WebKit Reporter: Geoffrey Garen <ggaren>
Component: New BugsAssignee: Geoffrey Garen <ggaren>
Status: RESOLVED FIXED    
Severity: Normal CC: clopez, oliver
Priority: P2    
Version: WebKit Nightly Build   
Hardware: Unspecified   
OS: Unspecified   
See Also: https://bugs.webkit.org/show_bug.cgi?id=180910
Attachments:
Description Flags
Patch mark.lam: review+

Geoffrey Garen
Reported 2016-12-06 17:04:51 PST
performance.now() should truncate to 100us
Attachments
Patch (1.13 KB, patch)
2016-12-06 17:05 PST, Geoffrey Garen 		mark.lam: review+
DetailsFormatted DiffDiff
View All Add attachment proposed patch, testcase, etc.
Geoffrey Garen
Comment 1 2016-12-06 17:05:31 PST
Created attachment 296354 [details] Patch
Mark Lam
Comment 2 2016-12-06 17:13:02 PST
Comment on attachment 296354 [details] Patch r=me.
Geoffrey Garen
Comment 3 2016-12-07 10:40:11 PST
Committed r209462: <http://trac.webkit.org/changeset/209462>
Chris Dumez
Comment 4 2016-12-08 12:05:04 PST
Comment on attachment 296354 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=296354&action=review > Source/WebCore/page/Performance.cpp:217 > + const double resolutionSeconds = 0.0001; Spec says: A DOMHighResTimeStamp should represent a time in milliseconds accurate to 5 microseconds
Geoffrey Garen
Comment 5 2016-12-08 12:12:25 PST
Yeah, we disagree with that behavior.
Carlos Alberto Lopez Perez
Comment 6 2018-01-05 11:43:31 PST
(In reply to Geoffrey Garen from comment #5) > Yeah, we disagree with that behavior. I guess then is worth adding a comment explaining that this is done on purpose, and to let know about it to anyone that feels like fixing this back to follow the spec.
Note You need to log in before you can comment on or make changes to this bug.