New issue
Advanced search Search tips

Issue 868774 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 798535
Owner: ----
Closed: Aug 2
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 2
Type: Bug



Sign in to add a comment

mouseover/mouseout fire improperly when display element alternately

Reported by liuhao...@gmail.com, Jul 30

Issue description

UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.99 Safari/537.36

Steps to reproduce the problem:
1. Open `index.html` in Chrome
2. Switch to `Console` tab of browser devtools
3. Click many times `Click!` text quickly

What is the expected behavior?
Console output nothing

What went wrong?
mouseover/mouseout fired when clicking `Click!` element

Did this work before? N/A 

Does this work in other browsers? N/A

Chrome version: 67.0.3396.99  Channel: stable
OS Version: 10.0
Flash Version: 

I can reproduce this issue on chrome canary 70.0.3506.0, but it's very different.
 
index.html
1.6 KB View Download
Video_2018-07-30_123011.mp4
2.0 MB View Download
Correction:
What is the expected behavior?
Console output nothing when clicking `Click!` element.

AFAIK, firefox/msedge works properly
Components: Blink>Input
Bisected to 3963e231e4c43187a05f3c6420f5df997d734ea0
"Send Mouse Leave events all the time when we get a ET_MOUSE_EXITED"
Landed in 57.0.2975.0

Simplified repro:
1. open the attached test.html
2. click the "Click" text 100 times without moving the mouse

Expected: only one initial "mouseover" shown
Observed: more than one "mouseover" or "mouseout" shown

Clicking can be done easily if you install AutoHotKey https://autohotkey.com
1. create a new file named click100.ahk 
2. put "F1::click 100" without quotes into the file
3. doubleclick the file to run it
4. point the mouse cursor over the target and press F1 key one time.
test.html
786 bytes View Download
Labels: Needs-Triage-M67
Labels: Triaged-ET Target-70 M-70 FoundIn-70 OS-Linux OS-Mac
Status: Untriaged (was: Unconfirmed)
Able to reproduce the issue on Mac 10.13.3, Win-10 and Ubuntu 14.04 using chrome reported version #67.0.3396.99 and latest canary #70.0.3506.0.
This is a non-regression issue as it is observed from M60 old builds. 

Hence, marking it as untriaged to get more inputs from dev team.

Thanks...!!
Cc: bokan@chromium.org
Mergedinto: 798535
Status: Duplicate (was: Untriaged)
Looks like issue 798535

Sign in to add a comment