Issue metadata
Sign in to add a comment
|
Mousedown event stopped working for position absolute elemnts
Reported by
o...@hindsiteinc.com,
Dec 21 2016
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.95 Safari/537.36 Steps to reproduce the problem: In chrome 55: Create a div and set position:absolute to it. Attach mousedown event. Observe that it's not being triggered. Simple jsfiddle test: http://jsfiddle.net/aYtUH/12/ What is the expected behavior? Event must be triggered What went wrong? Event is not being triggered in the latest version of chrome 55 Did this work before? Yes 54 Chrome version: 55.0.2883.95 Channel: stable OS Version: OS X 10.11.6 Flash Version: Shockwave Flash 24.0 r0
,
Dec 22 2016
There's a problem with your jsfiddle though: the log element is beneath the red rectangle in z-order so it takes 10+ clicks to make the log visible. Are you sure this is not the case here?
,
Dec 22 2016
,
Dec 22 2016
Tested the issue on windows-7, Mac-10.12.2 and Linux Ubuntu-14.04 using chrome stable version 55.0.2883.87 and latest canary 57.0.2958.3 with the steps mentioned above. Observed that the event was triggered with 12 mouse clicks. Same behavior observed in Firefox too. Please find the attached screen-cast and could you please let us know if anything missed here to reproduce the issue. Thanks..
,
Dec 22 2016
We couldn't properly isolate the issue from the app, so please close/remove this ticket for now.
,
Dec 23 2016
Thanks for the update, closing as per C#6. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 Deleted