Full screen should fully capture keyboard

[ghjm]

When in full screen mode in Chrome 132 on Windows 11, many key combinations such as Alt-Tab, Crtl-Esc and so on, activate local Windows functions rather than being sent to the remote device. When in full screen mode, the keyboard should be fully captured and always sent to the remote device.

[williamjohnstone]

I am looking at implementing this as part of my PR (#116).

https://developer.mozilla.org/en-US/docs/Web/API/Keyboard_API

"Keyboard locking enables a web page to capture keys that are normally reserved by the user agent or the underlying operating system. The intended use of the Keyboard API is by web applications such as games or remote access apps that provide a fullscreen immersive experience."

[tutman96]

I am looking at implementing this as part of my PR (#116).

https://developer.mozilla.org/en-US/docs/Web/API/Keyboard_API

"Keyboard locking enables a web page to capture keys that are normally reserved by the user agent or the underlying operating system. The intended use of the Keyboard API is by web applications such as games or remote access apps that provide a fullscreen immersive experience."

I've done a similar thing in the past with a tangental bit of software that I wrote: https://github.com/pod-arcade/client-web/blob/main/packages/session/src/components/Keyboard.tsx. It is a bit of complexity to make sure the state is synchronized between being fullscreen and fully capturing the keyboard.

[williamjohnstone]

Thank you for this @tutman96 I've had a really quick look, and I think it should help with my implementation, I might actually leave it open for another PR tbh, because my work load has changed a lot and not had much time to work on OSS.

[adamshiervani]

A few versions ago we introduced support for the Pointer Lock and Keyboard Lock APIs, which significantly improve Relative Mode.

The UX is not great, but after enabling "Relative Mode" you need to enable HTTPS Mode, as the Lock APIs only work in HTTPS. You can do that in Settings > Access. The easiest would be to pick "Self-Signed" and then point the browser to https://<jetkvm_ip>. Once you're access the dashboard, in HTTPS mode with relative mode, you should be able to use the Lock APIs.

I'll close the issue, but please don't hesitate to comment if it's still affecting you, and I'll reopen it, and we can continue tracking this.