[Webkit-unassigned] [Bug 154246] Use high resolution timestamp for event time

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=154246

Majid Valipour <majidvp at chromium.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |majidvp at chromium.org

--- Comment #3 from Majid Valipour <majidvp at chromium.org> ---
Here is some update on this feature:

High resolution event timestamps has been shipped in Chrome since M49[1] (released March 2016) and in Firefox stable since M54 [2] (released June 2017) and in Microsoft Edge Since EdgeHTML 14 [3].  WHATWG DOM spec has been updated [4] to reflect this with appropriate tests upstreamed to web-platform-tests.

Also we have received very positive feedback from Facebook [5] about the usefulness of high resolution event timestamp in scroll performance investigations.

I think at this point it is pretty safe to make the conversion given that it has been shipping for a while in 3 major browsers and our experience so far has been that backward compatibility issues are reasonably small and manageable.



[1] https://www.chromestatus.com/feature/5523910145605632
[2] https://developer.mozilla.org/en-US/Firefox/Releases/54
[3] https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/12726672/
[4] https://dom.spec.whatwg.org/#dom-event-timestamp
[5] https://github.com/whatwg/dom/issues/23#issuecomment-249319401

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20170908/3f978dcb/attachment.html>