[
https://issues.apache.org/jira/browse/GUACAMOLE-989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17095825#comment-17095825
]
Nick Couchman commented on GUACAMOLE-989:
-----------------------------------------
Also, looking at the code proposed by [~Toff], this would be dependent upon
GUACAMOLE-124, as we would have to programmatically know that we were going
into Full Screen mode before locking the keyboard. I would be opposed to a
change that locks the keyboard by default as soon as the client starts - this
would defeat several things, like the hidden menu (Ctrl-Alt-Shift) that are
core designs of Guacamole.
> Add support for chromium keyboard lock allowing for system keys and shortcuts
> -----------------------------------------------------------------------------
>
> Key: GUACAMOLE-989
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-989
> Project: Guacamole
> Issue Type: New Feature
> Reporter: Aaron
> Priority: Minor
>
> When accessing guacamole in a browser it would be great to have full RDP-like
> keyboard key and shortcut access. It is very easy to perform actions by
> special shortcuts (ie, Windows+Key, Alt+Tab) local PC instead of the intended
> remote PC as well as CTRL key shortcuts on the local browser instead of the
> remote browser. Another problem is closing the guacamole tab by accident via
> Ctrl+F4 (I've done this several times!). Some similar issues were voiced in
> GUACAMOLE-121 regarding CTRL+W.
> Please add support for Chromium's system keyboard lock API which allows a
> rich keyboard experience in full screen mode (you hold ESC for 2 seconds to
> exit). This would allow using special keys and shortcuts that we use
> habitually, and habits are hard to break. So why break them? Instead add
> keyboard lock functionality.
> Main page: [https://www.chromestatus.com/feature/5642959835889664]
> W3C Spec: [https://wicg.github.io/keyboard-lock/]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
