Issue metadata
Sign in to add a comment
|
Pointer leave/out event sometimes misfires when clicking under load
Reported by
g.r.m.sc...@gmail.com,
Jan 1
|
||||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:64.0) Gecko/20100101 Firefox/64.0 Steps to reproduce the problem: 1. Go to a CPU-intensive website (watch a YouTube video) 2. Add a listener for pointerleave/pointerout/mouseout/... 3. Spam click anywhere on the document What is the expected behavior? The listener does not get called What went wrong? The event listener gets called a few times Did this work before? N/A Chrome version: 71.0.3578.98 Channel: n/a OS Version: 10.0 Flash Version:
,
Jan 2
Reporter@ Thanks for the issue. Request you to provide a sample file where listener events like pointerleave/pointerout/mouseout are called, which will help in further triaging of the issue. Thanks..
,
Jan 2
Hi, thanks for the quick reply. I have made a demo, but the issue only showed up when using the canvas intensively, so it could be related to it. The demo has three listeners that log into the console when they are called. An interval on the window will draw a line on the canvas every 10ms. When you spam click anywhere in the document, the listeners get called sometimes.
,
Jan 2
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jan 5
,
Jan 9
Unable to reproduce the issue on reported chrome version 71.0.3578.98 using Windows 10. Attaching screen-cast for reference. Steps: ------ 1. Launched reported chrome 2. Opened given html file 3. Opened Devtools >Console and moved mouse in and out of the document As we have observed that the mouseleave and pointerout events @Reporter: Request you to retry this issue with fresh profile without any extensions & apps or reset all the flags and let us know if issue still persists. Thanks.!
,
Jan 9
Hi, thank you for your time. I believe I've not been clear on what the problem was, my apologies. The events do always get called when they should; the problem is that they get called when they should NOT be called. This happens when you spam-click somewhere in the document. I've recorded how it appears, but I had to change the drawing speed from 10 to 0 ms for the problem to appear, for some reason it wouldn't happen when recording otherwise.
,
Jan 9
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jan 9
,
Jan 10
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by swarnasree.mukkala@chromium.org
, Jan 2