I know this has been discussed ad nauseam but after reviewing a dozen threads I can’t find a single explanation as to why, just workarounds and instructions to use a proper ssh connection etc.
Browser event handlers for clipboard actions and context menus have unfortunately been led to allow preventing event bubbling (mostly for WYSIWYG editors, as far as I can tell), which is widely abused to annoy people who try to right-click-save an image (instead of opening it in the inspector?) or block the use of better passwords by interfering with password managers. The TrueNas shell interface does this for reasons that I have yet to grasp – is there any clear explanation?
I use a minimal keyboard and I don’t have an Insert key. I can hypothetically create a macro for relevant keycodes but in 20 years of using in-browser terminal emulation (and having written some) I have never run into any reason for disabling the context menu. What am I missing?
Do sites still try to block saving images? Anyway, 99% of people trying to save an image will not inspect source, and a 99% effective solution is still better than a 0% effective one. For the sites that interfere with password managers, it annoys me too but I’ve always assumed it was intended to cause problems for automated interaction with the password field, maybe for password spraying or capturing – which again can be worked around but it goes back to the ‘better than nothing’ thing.
Why you can’t use context menus to copy/paste from the shell? I dunno. Maybe the shell emulation isn’t developed by the team and blocks it? Control how copy/paste is handled to avoid unintended issues from browsers?
