[
https://issues.apache.org/jira/browse/GUACAMOLE-989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17095828#comment-17095828
]
Robert Hardy edited comment on GUACAMOLE-989 at 4/29/20, 7:38 PM:
------------------------------------------------------------------
[~vnick] Understood the priorities are different.
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.
Please realize from an end user usability point of view, in my opinion, I
would tag it critical.
I realize that is one user opinion.
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.
[~Toff] I've dusted off a Chromium browser just to attempt to use your
FullScreenGrabKeyboard.user.js.
I'm sick of losing sessions every time I delete a word when using Firefox.
Apparently Tampermonkey does exist for Chromium as well.
Are you installing FullScreenGrabKeyboard.user.js into guacamole 1.1 directly
or are you injecting using Tampermonkey or something similar to apply it?
was (Author: delemas):
[~vnick] Understood the priorities are different.
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.
Please realize from an end user usability point of view, in my opinion, I
would tag it critical.
I realize that is one user opinion.
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.
[~Toff] I've dusted off a Chromium browser just to attempt to use your
FullScreenGrabKeyboard.user.js.
I'm sick of losing sessions every time I delete a word when using Firefox.
Apparently Tampermonkey does exist for Chromium as well.
How are you installing FullScreenGrabKeyboard.user.js into guacamole 1.1
directly or are you injecting using Tampermonkey or something similar?
> 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)
