[
https://issues.apache.org/jira/browse/GUACAMOLE-989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17095767#comment-17095767
]
Robert Hardy commented on GUACAMOLE-989:
----------------------------------------
This currently tagged as minor, and it doesn't really help me but it is the
first attempt to actually fix an issue that drives me batty when using
guacamole. Please consider raising the priority. The issues this addresses is
crippling end users trying to use guacamole.
End users shouldn't need to consider custom browser compiles only to not have
critical UI issues when using guacamole.
Basically the browser intercepts something destined to my text editor and does
unwanted things.
The worst of which is CTRL w which in many text editor normally deletes a word
which I try to use all the time.
Of course Firefox promptly destroys my session closing my guacamole tab in my
browser.
During the switch to web extension addons Firefox disabled all the addons which
used to allow customization of keyboard short cuts.
One currently has to hack the browser code or worse recompile it to get a
browser without the CTRL w.
If we can get chromium working with Toff's FullScreenGrabKeyboard.user.js to
"lock" the keyboard, we may be able nudge Firefox development hard enough that
"this works properly in chromium please fix this use case" and they might
actually do it.
> 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)
