Disabled Elements still work in Chrome via touch or pointer events
Reported by
aas...@kleinbuendel.com,
Aug 11
|
|||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/68.0.3440.106 Safari/537.36 Steps to reproduce the problem: 1. make button element disabled via markup or javascript 2. add listener to the button using either a touch event or pointer event 3. touch or click button. If using touch event put chrome in emulation mode or test on touch device. What is the expected behavior? callback function should NOT be executed nothing should happen What went wrong? callback function IS executed Did this work before? N/A Chrome version: 68.0.3440.106 Channel: stable OS Version: OS X 10.11.6 Flash Version: Can see here on CodePen: https://codepen.io/aashby13/pen/YjBpGj I've tested on Chrome on a macOS desktop and on a Microsoft Surface 2. Other browsers do not behave this way.
,
Aug 13
,
Aug 16
This was intentional and by design. Here is the spec issue: https://github.com/w3c/pointerevents/issues/177 Olli, is that something you can track in Firefox and have that behavior? Reporter, if you care about the activation of the element you should listen to the click event which goes away when the element is disabled. |
|||
►
Sign in to add a comment |
|||
Comment 1 by swarnasree.mukkala@chromium.org
, Aug 12