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

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

[~Delemas]
{quote}
I would love to try that pull but I'm still hamstringed by the lack of a 1.2.0 
release tar. I will try it eventually.
I am building a new guac 1.2.0 VM where I upgraded to Ubuntu 20.04 to get the 
new Tomcat.
Upgrading my OS I ended up with an upgraded database but in an environment that 
guac 1.1.0 cannot connect to. Once the guac 1.2.0 gets posted I believe I 
should be able get the database driver to work.
{quote}

Understood.  This feature won't be in the 1.2.0 release - it'll be in 1.3.0.  
We'll release a 1.2.0 release tar when we release 1.2.0 - it isn't ready, yet.

> 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