New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 801058 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Jan 2018
Cc:
Components:
EstimatedDays: ----
NextAction: 2018-02-01
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

(Debian 9 64-bit) mousemove, mouseenter, and mouseleave not Firing Without Clicking

Reported by bubbler...@gmail.com, Jan 11 2018

Issue description

UserAgent: Mozilla/5.0 (X11; Linux x86_64; rv:57.0) Gecko/20100101 Firefox/57.0

Steps to reproduce the problem:
1. Open the following JSFiddle in Chrome: http://jsfiddle.net/xfFMk/591/.

2. Mouse over the "Mouse Test" text with the console open.

3. Observe that the event listeners do not fire properly unless the text is clicked.

What is the expected behavior?
onmouseenter, onmouseleave, and onmousemove events should all fire without the mouse needing to be clicked.

What went wrong?
The events listed above do not fire without clicking the mouse. For example, onmouseenter and onmousemove only fire when the element with the listeners is clicked. onmouseleave only fires when an area outside of that element is clicked.

Did this work before? N/A 

Chrome version: Version 63.0.3239.132 (Official Build) (64-bit)  Channel: n/a
OS Version: Debian 9 64-bit, Kernel Version 4.9.0-5-amd64
Flash Version:
 

Comment 1 by tkent@chromium.org, Jan 11 2018

Components: -Blink Blink>Input
Labels: Needs-Triage-M63
I don't seem to be able to repro this. The events fire just fine for me. Can you record a screen cast of this? Do you happen to have any extensions installed or something?
I can confirm that this still happens with no extensions enabled. Please see my attached screen cast.
screencap.mp4
774 KB View Download
Cc: sc00335...@techmahindra.com
Labels: Triaged-ET Needs-Feedback
Unable to reproduce this issue on reported version 63.0.3239.132 using Ubuntu 14.04 with below steps.

1. Navigated to http://jsfiddle.net/xfFMk/591/ and opened devtools console.
2. Hovered mouse on Mouse test and observed mouse entered,moved and left events successfully.

@Reporter: Could you please check the video and let us know if we miss anything. This would help in further triaging of the issue.

Thanks!
issue 801058.ogv
2.9 MB View Download
@sc00335...@techmahindra.com: The way you attempted to reproduce the issue is correct. Only difference I notice is the OS you used. I will also note that I'm using KDE Plasma 5 as my window manager, if that perhaps has some effect.
Project Member

Comment 7 by sheriffbot@chromium.org, Jan 12 2018

Labels: -Needs-Feedback
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
Cc: vamshi.k...@techmahindra.com
Labels: TE-NeedsTriageFromHYD
As per comment#6 by the reporter feels like the issue seems to be reroduced using KDE Plasma 5, ET team has tried setting up that environment in Ubuntu 14.04, but we are unable to do as there are few package issues associated with it. Hence requesting someone from TE-Hyd team to have a look into this issue for further investigation. Hence adding label TE-NeedsTriageFromHYD.

Thanks!

Comment 9 by bokan@chromium.org, Jan 18 2018

Cc: bokan@chromium.org
bubblerugs@: I notice in the screen case you have device emulation turned on with a device using touch (that's why the mouse cursor is a circle). In that case, we're simulating using a touch screen which won't send mousemove, enter, exit events. Does it work if you turn off emulation (or use a device that doesn't emulate touch - e.g. "Laptop with MDPI screen"

Comment 10 by bokan@chromium.org, Jan 18 2018

Labels: Needs-Feedback
NextAction: 2018-02-01
Ah...@bokan you are absolutely correct. My mistake. I had not even considered the fact that I was using device emulation. Turning off emulation produced the expected behavior for me. Thank you for getting to the bottom of this, and my apologies for the false alarm!
Project Member

Comment 12 by sheriffbot@chromium.org, Jan 19 2018

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "bokan@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
Cc: kkaluri@chromium.org
Status: WontFix (was: Unconfirmed)
As per comment #11 closing this issue
The NextAction date has arrived: 2018-02-01

Sign in to add a comment