Support Article
Button click event on an element triggers click event on another
SA-29050
Summary
On mobile browsers, when users click/tap on a particular element(e.g. button) of the screen, the click event is erroneously triggered for a second element(e.g. checkbox) that would turn up in the first element's(button) position. This second element appears on the screen as a consequence of actions configured on the first element(button).
Error Messages
Not Applicable
Steps to Reproduce




Root Cause
There is delay in browser events in case of mobile devices. Synthetic events are fired in device to prevent the 300ms delay. But after 300ms the actual event is also getting fired. Solution is to prevent the actual click event from being propagated in mobile devices.
Resolution
Apply HFix-30093
Published October 27, 2016 - Updated October 8, 2020
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.