Exit Full Screen (Esc) has to be changed to i.e. F11

[Jozef-sk40]

I need to connect to Linux server, where I very often need to press ESC key (i.e. while using vim or mc).
Is there a way to change ESC key to Firefox common exit key F11 ?

[IDisposable]

This was fixed in PR #535 which has been merged to DEV, but MAIN (where the autoupdate releases from) hasn't gotten a merge from DEV in quite a while. @ym any idea when we can see all the cool stuff in DEV make it out?

[am-zed]

This works for Google Chrome but not Firefox or Chromium.

[Novido]

I'd love the ability to change the key-binding for exiting fullscreen as I use the ESC quite frequently.

[Jozef-sk40]

So, as u can see, the only probelm is, the "ESC exit full-screen" is hardwired inside JetKVM app,
where I can see { event.key === "Escape" } multiple times.
So I would say, the problem is solvable ...

[DonOregano]

1. Type about:config into the Firefox address bar and press Enter.
2. Click Accept the Risk and Continue if a warning message appears.
3. In the search bar, type browser.fullscreen.exit_on_escape.
4. If the value is true, click the toggle button on the right to change it to false.
5. Close the about:config tab.

This does not work for me. I think that option has been removed from firefox. Which is super annoying, but also not the fault of JetKVM...

[IDisposable]

Probably already know this, but you have to be SSL to enable the long press, so https://

[DonOregano]

No, I did not know that! But that only works in chromium for me. Firefox still exits fullscreen on short press escape.

[IDisposable]

That sounds like a bug in Firefox :)

Seriously... looks like it's coming #535 (comment)

[jdranchman]

Any traction on getting this fixed and/or the code pushed to main?

[IDisposable]

There is NO WAY for the code to be changed. This is a by-design decision of the Web Browser spec authors to prevent web-page from maliciously taking over the entire screen with no guaranteed way to exit the full-screen. The ESC key is hard-coded in all browsers.

The only this we can do is lock the keyboard, which we do, but that ONLY is allowed if the page is loaded from https:// or http://localhost (the second one to support people trying to develop pages that do this safely).

[jdranchman]

The biggest problem I have now is the console resolution sucks on the standard web display and everything is fuzzy. Going full screen is the only way I can read what is there. It is a royal PITA to flip to full screen to read and back to edit and back to full screen to see if what I typed was even right (with vi, shell whatever that uses ESC all the time). Maybe consider making an "almost full screen" mode that doesn't rely on default browser behavior for the typical full screen/ESC issue? This might require some sort of resizing that would be a pita in itself.

[IDisposable]

Maybe consider making an "almost full screen" mode that doesn't rely on default browser behavior for the typical full screen/ESC issue?

That's on the roadmap! We're thinking of a full-screen-ish that has a draggable (to move it where it's not in the way) hover-over widget for doing everything