[
https://issues.apache.org/jira/browse/GUACAMOLE-989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17095844#comment-17095844
]
Nick Couchman commented on GUACAMOLE-989:
-----------------------------------------
{quote}
I will be very glad when a packaged guacamole 1.2.0 built against packaged
freerdp 2.0 is released. All these snapshot releases built using bash scripts
are highly unmaintainable.
{quote}
Yeah, if you're using it in any sort of a production environment I'd stick with
the released code - 1.1.0 - for the time being. We are working on 1.2.0, and
we're already piling up the issues and fixes for 1.3.0 to follow that. But, I
think everyone's day jobs have gotten busier lately, so it's been hard to fit
in the time to contribute and review.
{quote}
Really the intercept is needed outside of full screen mode too but the first
step is replicating a fix of any sort even if I have to compile a custom
browser to do that.
My dream is to have a check box on guacamole CTRL ALT SHIFT screen that says
intercept all allowable keyboard input for this tab except CTRL ALT SHIFT. That
would solve so many problems above and beyond CTRL w.
{quote}
I wouldn't be opposed to some sort of option within the hidden menu that
enables the keyboard lock and then closes the hidden menu. This seems
reasonable.
> 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)
