Issue metadata
Sign in to add a comment
|
MouseLeave triggered on fast mouse clicks
Reported by
santiago...@gmail.com,
Sep 23 2017
|
||||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.91 Safari/537.36 Steps to reproduce the problem: 1. add listener to click event to a div with a console.log for it. 2. add listener to mouseleave to the same div also with a console.log. 3. click fast on that div. See JSFiddle: https://jsfiddle.net/sjo1hk7w/ What is the expected behavior? No mouseleave event should be triggered. What went wrong? mouseleave event is fired ocatinally even though the mouse never left the div. Did this work before? N/A Does this work in other browsers? Yes Chrome version: 61.0.3163.91 Channel: stable OS Version: 10.0 Flash Version:
,
Sep 25 2017
,
Sep 25 2017
Unable to reproduce this issue on 61.0.3163.91 and on canary 63.0.3222.0 using Windows 10 with steps mentioned below. 1.Navigated to https://jsfiddle.net/sjo1hk7w/ >> Opened devtools console 2.Clicked on div for 40-50 times and no mouse leave event is triggered. Attaching screencast of same @Reporter: Could you let us know if we missed any steps from our end and also please check the issue on fresh profile with no extensions or apps? Thanks!
,
Sep 25 2017
In 61.0.3163.100 now, the same here. I tried with a clean profile and had the same problem. Here's a screen capture of the issue.
,
Sep 25 2017
Thank you for providing more feedback. Adding requester "sc00335628@techmahindra.com" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Sep 25 2017
I tried on a different machine, same error. It seems like the mouse needs to move just a few pixels for the mouseleave to trigger. It doesn't seem to happen as often if the mouse is standing still.
,
Sep 26 2017
@Reporter: Tried moving the cursor while clicking, in order to get any mouse leave event to get recorded. But, it didn't record any event while clicking in the red colored portion until and unless it's moved out of that region. Please find the attached screencast and let us know the update.
,
Sep 26 2017
May you please try on a few different computers? We are getting this in two of ours, only in Chrome, Firefox works fine.
,
Sep 27 2017
We are unable to reprouduce the issue on windows 7 & 10 both laptop & desktop on stable M61 #61.0.3163.100 . @santiagopuentep-- Could you please provide us the screencast of the issue , and your chrome://gpu details , that would help us in further traiging. Thanks!
,
Sep 27 2017
Here are the GPU details.
,
Sep 27 2017
Here is the screencast of the problem (it is the same provided in an earlier comment).
,
Sep 27 2017
Thank you for providing more feedback. Adding requester "hdodda@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Sep 28 2017
Re-tried the issue again on Windows 7 and Mac OS 10.12.6 using the latest Stable 61.0.3163.100 and latest Canary 63.0.3226.0 and unable to reproduce the issue. Requesting someone from 'Blink>Input' team to please look into this issue and help in further triaging. Thanks..
,
Sep 28 2017
Might be caused by the mouse driver software or some other OS utility that alters mouse behavior.
,
Sep 28 2017
Sorry your videos (in comment #11 and #4) aren't loading for me (I tried to play them on ChromeOS and Mac). You are certain you don't have any extensions installed right? And it still fails in incognito mode right? Are you able to provide an input trace? See https://www.chromium.org/developers/how-tos/trace-event-profiling-tool/recording-tracing-runs Do you have any specific hardware installed? Like Logitech mouse support?
,
Oct 5 2017
@santiagopuentep - Could you please respond to C#15. Thanks!
,
Oct 5 2017
Still waiting on feedback.
,
Oct 5 2017
Sorry for the late response, I was traveling. Here it is in mp4.
,
Oct 5 2017
Thank you for providing more feedback. Adding requester "pnangunoori@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Oct 5 2017
I tryied with all extensions disabled and in incognito mode and the bug is still there. Here is the stack trace. The first mouseleave is the buggy one, the second one is due to movement to stop the recording. The only hardware installed is a simple usb mouse, nothing fancy. This bug doesn't happen on Firefox.
,
Oct 9 2017
Able to reproduce on reported version #61.0.3163.91, latest stable #61.0.3163.100 and latest Canary#63.0.3235.0 with the mentioned steps on Ubuntu 14.04, windows 7 and Mac 10.12.6. This seems to be a Non-Regression issue seen from M-50[50.0.2624.0]. Hence, marking it as Untriaged
,
Oct 12 2017
The NextAction date has arrived: 2017-10-12
,
Oct 12 2017
kebalaji@ We can't seem to reproduce this. Can you attach a screen recording? I'm trying to figure out how this is actually occurring.. it definitely shows MouseLeave getting generated. santia...@ I presume you don't have any MSDN devtools installed on this machine that you could capture a spy++ trace.
,
Oct 19 2017
kebalaji@ ping. Do you mind attaching your screen cast as well as your input trace? See https://www.chromium.org/developers/how-tos/trace-event-profiling-tool/recording-tracing-runs
,
Nov 16 2017
Unfortunately, this isn't actionable without additional data or a reproduction on our end. I'm going to close for now. Feel free to reply with additional information and we can reopen.
,
Jan 12 2018
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by hayato@chromium.org
, Sep 25 2017