You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@guacamole.apache.org by "Aaron (Jira)" <ji...@apache.org> on 2020/05/21 17:27:00 UTC
[jira] [Comment Edited] (GUACAMOLE-989) Add support for chromium
keyboard lock allowing for system keys and shortcuts
[ https://issues.apache.org/jira/browse/GUACAMOLE-989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17113408#comment-17113408 ]
Aaron edited comment on GUACAMOLE-989 at 5/21/20, 5:26 PM:
-----------------------------------------------------------
According to all of the documentation for Keyboard Lock, Alt+Tab and other system key combinations are designed to work. It was basically built for this exact purpose, so it not working would be a bug or configuration problem vs expected behavior.
From [https://www.chromestatus.com/feature/5642959835889664|https://www.chromestatus.com/feature/5642959835889664)]:
{quote}While in fullscreen, this API allows apps to receive keys that are normally handled by the system or the browser like Cmd/Alt-Tab, or Esc.
{quote}
From [https://github.com/WICG/keyboard-lock/blob/gh-pages/explainer.md|https://github.com/WICG/keyboard-lock/blob/gh-pages/explainer.md)]:
{quote}All the browser and OS shortcuts, such as Cmd/Alt+Tab should be used to switch windows on the remote computer, while Escape can be used to cancel a command.
{quote}
From [https://wicg.github.io/keyboard-lock/]:
{quote}Some examples of the keys that may be required are Escape, Alt+Tab, Cmd+`, and Ctrl+N.
By default, these keys are not available to the web application because they are captured by the browser or the underlying operating system. The Keyboard Lock API enables websites to capture and use all available keys allowed by the OS.
{quote}
was (Author: acplex):
According to all of the documentation for Keyboard Lock, Alt+Tab and other system key combinations are designed to work. It was basically built for this exact purpose, so it not working would be a bug or configuration problem vs expected behavior.
From [https://www.chromestatus.com/feature/5642959835889664|https://www.chromestatus.com/feature/5642959835889664)]:
{quote}While in fullscreen, this API allows apps to receive keys that are normally handled by the system or the browser like Cmd/Alt-Tab, or Esc.
{quote}
From [https://github.com/WICG/keyboard-lock/blob/gh-pages/explainer.md|https://github.com/WICG/keyboard-lock/blob/gh-pages/explainer.md)]:
{quote}All the browser and OS shortcuts, such as Cmd/Alt+Tab should be used to switch windows on the remote computer, while Escape can be used to cancel a command.
{quote}
From [https://wicg.github.io/keyboard-lock/]:
{quote}Some examples of the keys that may be required are Escape, Alt+Tab, Cmd+`, and Ctrl+N.
By default, these keys are not available to the web application because they are captured by the browser or the underlying operating system. The Keyboard Lock API enables websites to capture and use all available keys allowed by the OS.
{quote}
> 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)