[
https://issues.apache.org/jira/browse/GUACAMOLE-989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17112386#comment-17112386
]
Nick Couchman commented on GUACAMOLE-989:
-----------------------------------------
[~odairmun]:
Thank you for your input. A few points:
* However, I have already attempted an implementation and have asked for people
to try it out. I have no feedback on it, yet.
* I also continue to question how valuable this will really be, since even the
Chromium Keyboard Lock will not prevent the operating system from intercepting
key combinations.
* That said, I believe it is likely we will implement it in some form or
another (maybe not exactly as it is today), but it will not be in the 1.2.0
release.
> 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)
