Issue metadata
Sign in to add a comment
|
Once you touch an element, hover stays on element even after interacting with other elements
Reported by
moosa.es...@pearson.com,
Jul 11 2016
|
||||||||||||||||||
Issue descriptionUserAgent: 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 im testing on surface touch.
,
Jul 11 2016
also created a bug with jquery-ui since im not sure if this is a browser bug or jquery-ui https://bugs.jqueryui.com/ticket/15005#ticket
,
Jul 13 2016
Issue is reproducible on Win 10(Dell Precision M3800 touch screen) on stable 51.0.2703.106 and canary 54.0.2794.0. Observing the same behavior since M 35.0.1898.0, hence Untriaged this as a non-regression issue. Note : Working fine on FireFox 47.0.1.
,
Jul 13 2016
correcting Chrome version # 51.0.2704.106.
,
Jan 20 2017
Any updates on this issue?
,
Aug 8
Any update on this? |
|||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||
Comment 1 by moosa.es...@pearson.com
, Jul 11 2016