# Perspective touchscreen long press context menu **URL:** \ **Category:** Ignition\ **Tags:** ignition83, perspective\ **Created:** [March 8, 2026, 1:05pm UTC](https://forum.inductiveautomation.com/t/perspective-touchscreen-long-press-context-menu/114384 "2026-03-08T13:05:49Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![Robbe\_Meyvis](https://avatars.discourse-cdn.com/v4/letter/r/e68b1a/32.png) [@Robbe\_Meyvis](https://forum.inductiveautomation.com/u/Robbe_Meyvis)\ **Post date:** [March 8, 2026, 1:05pm UTC](https://forum.inductiveautomation.com/t/perspective-touchscreen-long-press-context-menu/114384/1 "2026-03-08T13:05:49Z")
**Version: Ignition Edge 8.3.3** I need to have a jog button to run something as long as the button is pressed. To do this, I made a button with 2 events: onMouseDown and onMouseUp which sets and resets a bit. This works fine when using a mouse. However: with a **touchscreen** , I experience **right-click behaviour** : ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/b/b/bb551bb46f50e973421942070e9daa6cf88b8046.png) I tried disabling the press-and-hold right click setting: ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/9/2/920fb120eb2feb7068a5a40626cb6e8ec9aed4a6.jpeg) But it still didn’t work. Still get the context menu. I was reading these topics: > [@Perspective Touchscreen Long Press](https://forum.inductiveautomation.com/t/perspective-touchscreen-long-press/67766): > > We have an issue with longpress on buttons on touchscreen HMI using perspective. A copy Menu popsup ? we have disabled "right mouse" emulation under control panel "touch and pen" we want to use the buttons for jogging motors. Problem occurs on any button including navigation buttons. > [@Perspective Mouse event, disable cut/copy/paste on iPad](https://forum.inductiveautomation.com/t/perspective-mouse-event-disable-cut-copy-paste-on-ipad/25650): > > We use a lot of mousedown/mouseup events on our old mobile module on Ignition v7.9. This allows us to set a OPC tag to 1 on mousedown, and then 0 on mouseup. (Moving equipment from iPad screen). I’m trying to recreate this on perspective. I use the onTouchStart event and onTouchEnd event to accomplish this. I couldn’t get the onMousedown and onMouseUp events to work with Perspective properly. While it works, since now it’s HTML5 i guess, I can get a popup on the iPad when I hold down the button… > [@Perspective disable right click menu on touchscreen](https://forum.inductiveautomation.com/t/perspective-disable-right-click-menu-on-touchscreen/65595): > > I am currently developing a Perspective app using Ignition 8.1 and using a Google Chrome on a Phoenix HMI Panel PC (has Windows 10 OS) for the session. One of the pages has a set of buttons used for motor control; hold down to write high to the PLC tag, release to write low to the PLC tag. If the button is held down for an extended duration, the right click context menu will pop up. I've disabled the NoViewContextMenu flag in the registry editor though this seems to just disable the right click… It seems that I need to add the following somewhere to a css file: ```python * { -webkit-touch-callout: none; -webkit-user-select:none; } ``` Tried adding it here but doesn’t work: ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/b/c/bc1315f236c943d9bdedaaa689a4c4f948eac94b.png) I’m not sure if I added it in the right place? Also tried to just add it to the button: ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/2/5/257957c4849e4cf1006314ea108a2807866a584b.png) But that also doesn’t work… I tried Chrome kiosk mode, then I don’t get the context menu. But I also cannot click the button with a long press… Any help is highly appreciated! ---
**Author:** ![Robbe\_Meyvis](https://avatars.discourse-cdn.com/v4/letter/r/e68b1a/32.png) [@Robbe\_Meyvis](https://forum.inductiveautomation.com/u/Robbe_Meyvis)\ **Post date:** [March 8, 2026, 2:31pm UTC](https://forum.inductiveautomation.com/t/perspective-touchscreen-long-press-context-menu/114384/2 "2026-03-08T14:31:30Z")
After fiddling a lot more, I found these touch events. I added the same scripts to set/reset the bit and now it works in Chrome Kiosk mode. ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/0/1/01fe32d1c8a12bd188e1fe0a9ea4f4084ecbb98b.png) If anyone has a better solution, I’d love to hear about that! ---
**Author:** ![michael.flagler](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/michael.flagler/32/26272_2.png) [@michael.flagler](https://forum.inductiveautomation.com/u/michael.flagler)\ **Post date:** [March 8, 2026, 3:25pm UTC](https://forum.inductiveautomation.com/t/perspective-touchscreen-long-press-context-menu/114384/3 "2026-03-08T15:25:52Z")
Everyone here will highly suggest you to not use a momentary button at all in perspective. You need to use start and stop buttons to accomplish this as you'll run into issues trying to use a momentary style button beyond what you've already experienced. ---
**Author:** ![nminchin](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/nminchin/32/6911_2.png) [@nminchin](https://forum.inductiveautomation.com/u/nminchin)\ **Post date:** [March 9, 2026, 2:04am UTC](https://forum.inductiveautomation.com/t/perspective-touchscreen-long-press-context-menu/114384/4 "2026-03-09T02:04:16Z")
> [@michael.flagler](#): > > beyond what you've already experienced. Most notably and notoriously that the momentary button will not turn off and leave your tag high ---
**Author:** ![micah.hastings](https://avatars.discourse-cdn.com/v4/letter/m/cc9497/32.png) [@micah.hastings](https://forum.inductiveautomation.com/u/micah.hastings)\ **Post date:** [March 10, 2026, 12:40pm UTC](https://forum.inductiveautomation.com/t/perspective-touchscreen-long-press-context-menu/114384/5 "2026-03-10T12:40:15Z")
I would agree that you should not use a momentary button if possible. In our situation, the operators really wanted this feature and we provided a fail safe button if it did get stuck. I also added some PLC timeout logic if this happened too. With that said, we use this all the time on a 24/7 operation and have zero issues. The CSS code was added to the following file: C:\program files\Inductive Automation\Ignition\data\modules\com.inductiveautomation.perspective\themes\light.css See screenshot for code added. ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/0/3/03e6ac791e2a956fb882dbe16aff75b841b195c6.png) ---
**Author:** ![nminchin](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/nminchin/32/6911_2.png) [@nminchin](https://forum.inductiveautomation.com/u/nminchin)\ **Post date:** [March 11, 2026, 9:40am UTC](https://forum.inductiveautomation.com/t/perspective-touchscreen-long-press-context-menu/114384/6 "2026-03-11T09:40:26Z")
> [@micah.hastings](#): > > The CSS code was added to the following file: > > C:\program files\Inductive Automation\Ignition\data\modules\com.inductiveautomation.perspective\themes\light.css I haven't tested it myself but I believe the standard theme files are replaced on ignition upgrade with defaults meaning you’ll lose your edits. Regardless, editing the base theme files is not recommended for multiple reasons such as mentioned above, inability to identify what modifications have been made to defaults which is particularly important for diagnosing potential issues that are a result of modifications, and others