Invalid Event.timeStamp value on mousemove |
||||
Issue descriptionOriginally reported by Ben. > I was able to write this code to demonstrate the issue. I can’t figure out how to actually reproduce it. I basically scroll, move my mouse and flip between tabs a bunch. Eventually I got a duration that was extremely large – far longer than I had opened my page for. It takes a while to repro – not very consistent at all. This was on a Mac with chrome stable. http://jsfiddle.net/9d2b4upe/3/embedded/result,html,js/ I have also been able to reproduce this. The oddball timestamp I see comes from mousemove events in particular.
,
Aug 31 2016
,
Aug 31 2016
,
Feb 4 2017
Any update on this?
,
Feb 9 2017
I cannot reproduce the exact issue anymore on latest Canary. I did reproduce a similar issue if I right click and bring up context menu. I have a fix for it here [2]. dtapuska@ recently made WebInputEvent (and platform event) timestamp initialization a bit more robust to prevent uninitialized values and in the process caught and fixed a few cases. The original case may have been in there. [1] [1] https://codereview.chromium.org/2569273002/ [2] https://codereview.chromium.org/2686723003/
,
Feb 13 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/f212cc56820dda5e8b5d902a15e39bcb09c37df5 commit f212cc56820dda5e8b5d902a15e39bcb09c37df5 Author: majidvp <majidvp@chromium.org> Date: Mon Feb 13 18:04:07 2017 Use correct timestamp for generated mouse events on Mac. BUG= 642737 Review-Url: https://codereview.chromium.org/2686723003 Cr-Commit-Position: refs/heads/master@{#450005} [modify] https://crrev.com/f212cc56820dda5e8b5d902a15e39bcb09c37df5/content/browser/renderer_host/render_widget_host_view_mac.mm [modify] https://crrev.com/f212cc56820dda5e8b5d902a15e39bcb09c37df5/ui/base/cocoa/tool_tip_base_view.mm
,
Feb 14 2017
Marking as fixed. Feel free to re-open if you see another case. |
||||
►
Sign in to add a comment |
||||
Comment 1 by dtapu...@chromium.org
, Aug 31 2016