Unexpected rAF callback time value |
||||
Issue descriptionhttp://jsbin.com/saqoxa/edit?js,console,output I expected the window.performance.now() value inside the click handler to temporally precede the time value passed to the rAF callback, on the basis that the click handler should be scheduling the rAF callback for the next frame. In Chrome on Mac (55.0.2880.0 canary), the rAF callback shows an earlier time than the click handler (see attached file). In Firefox, Safari, and Edge the value in click precedes rAF's, so we seem to be the exception.
,
Feb 21 2018
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. If you change it back, also remove the "Hotlist-Recharge-Cold" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Feb 27 2018
,
Aug 15
|
||||
►
Sign in to add a comment |
||||
Comment 1 by skyos...@chromium.org
, Feb 20 2017