[ 
https://issues.apache.org/jira/browse/GUACAMOLE-989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17095818#comment-17095818
 ] 

Nick Couchman commented on GUACAMOLE-989:
-----------------------------------------

[~Delemas]: I understand that it is a bigger deal for you and your user base.  
The priority is based on the priority for the project, overall, and we have 
several other things we're trying to finish up for the 1.2.0 release that trump 
this in terms of priority.

Also, this feature is based on a very new feature in Chrome (and _maybe_ other 
browsers), and is unlikely to be supported on many of the browsers that people 
accessing Guacamole would use.  So, while I totally agree that it would be a 
great feature to have implemented and I'm happy to see it added, I have trouble 
making it a major or critical priority.

> 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)

Reply via email to