# \[BUG-16346\] Button: onMouseDown event triggers on a Touch Event **URL:** \ **Category:** Ignition Early Access\ **Tags:** perspective\ **Created:** [April 16, 2020, 8:32pm UTC](https://forum.inductiveautomation.com/t/bug-16346-button-onmousedown-event-triggers-on-a-touch-event/33988 "2020-04-16T20:32:05Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![bmusson](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/bmusson/32/87530_2.png) [@bmusson](https://forum.inductiveautomation.com/u/bmusson)\ **Post date:** [April 16, 2020, 9:21pm UTC](https://forum.inductiveautomation.com/t/bug-16346-button-onmousedown-event-triggers-on-a-touch-event/33988/2 "2020-04-16T21:21:05Z")
I know this doesn't answer your mouse event question, but you should give this thread a read and evaluate exactly how your push-to-run logic is working. There is potential for danger here if done incorrectly. > [@Momentary Pushbutton latching ON](http://forum.inductiveautomation.com/t/momentary-pushbutton-latching-on/5373/60): > > Perhaps you didn’t grasp the core of the problem – it isn’t Ignition, it is the nature of request-response protocols. This problems exists in every product I’ve ever used over my 30 years in this business, with every brand of PLC and every brand of HMI. If they used a request-response protocol. Serial, ethernet, DH+, Siemens, Modicon, Allen-Bradley, and others. Even tag access over mixed technologies like DeviceNet and ControlNet. Didn’t matter. All showed this problem. Products that impl… --- _[View the full topic](https://forum.inductiveautomation.com/t/bug-16346-button-onmousedown-event-triggers-on-a-touch-event/33988)._