Context Menu needs to be tested on different browsers and operating systems

[Gideon Pinto]

One of the users was driving using Chrome on his computer. Once the full pipeline had been rendered, as a test I said "well let's anon that node". He right clicked and tried many times to choose "+ pipeline". It didn't work. Not sure how to debug that, but we tried going back to the Feed Table, back to the feed detail, right click on a node to select "+ pipeline".

Provide a fallback incase it doesn't work

[Gideon Pinto]

1. Browser Support: Custom context menus are not universally supported across all browsers. While they work in Chrome, they may behave differently or have limited support in other browsers like Firefox or Safari.
2. Event Handling: When creating custom context menus, you typically use JavaScript to handle the contextmenu event. This event is triggered when the user right-clicks on an element. However, some elements may have default context menus that override custom ones. For example, you cannot override the context menu for the browser's address bar or other browser-specific UI elements.
3. Content Security Policy (CSP): If your web page has a Content Security Policy (CSP) that restricts inline scripts or external resources, you may need to adjust the policy to allow the execution of scripts associated with custom context menus.
4. Browser Extensions: Some browser extensions or plugins may interfere with custom context menus. Users who have installed ad blockers or other similar extensions might experience unexpected behavior.
5. Mobile Devices: On touch-based devices like smartphones and tablets, custom context menus are generally not supported, as they rely on mouse-based interactions. Long-pressing on elements may trigger different behaviors depending on the browser and device.