Search and Top Navigation
#15005 closed bug (patcheswelcome)
Opened July 11, 2016 07:15PM UTC
Closed July 12, 2016 06:14PM UTC
Once you touch an element, hover stays on element even after interacting with other elements
Reported by: | moosazero | Owned by: | |
---|---|---|---|
Priority: | minor | Milestone: | none |
Component: | ui.draggable | Version: | 1.12.0 |
Keywords: | Cc: | ||
Blocked by: | Blocking: |
Description
UserAgent: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.103 Safari/537.36
Example URL:
http://jsfiddle.net/ncLu5j6n/5/
Steps to reproduce the problem:
if you touch elements with css for hover, multiple times
(sometimes going back and forth between two elements, helps to reproduce the issue faster)
You will get to a point where hover stays on one element and doesnt let go
more specifically in my example i have a yellow color for hovered div, if you touch multiple times between the two square, suddenly one of the divs would stay in hover state and it doesnt let go even when you try to drag the other dragger.
What is the expected behavior?
hover state should be gone once you interact with the page.
in this case with jquery draggers touching multiple times , should have any affect and hover shouldnt get stuck to the element.
What went wrong?
element stayed in hover state.
Does it occur on multiple sites: N/A
Is it a problem with a plugin? No
Did this work before? N/A
Does this work in other browsers? Yes
Chrome version: 51.0.2704.103 Channel: n/a
OS Version: 10.0
Flash Version: Shockwave Flash 22.0 r0
I'm testing on surface touch.
Here is the video :
https://drive.google.com/file/d/0B_OizdD4UkrbeFU2Sm8xS2NHdXc/view?usp=sharing
I also created a bug for chromium since this is happening there:
here is the link to that bug:
Attachments (0)
Change History (1)
Changed July 12, 2016 06:14PM UTC by comment:1
component: | ui.core → ui.draggable |
---|---|
resolution: | → patcheswelcome |
status: | new → closed |
version: | 1.11.3 → 1.12.0 |
Since this bug is about the native
:hover
styling, I don't think there's anything we can do about it. If someone can track down the actual cause and provide a patch, we can review it, but this seems like something Chrome has to fix.