www.cendio.com
Bug 4755 - Keyboard shortcuts gets intercepted by the browser when using Web Access
: Keyboard shortcuts gets intercepted by the browser when using Web Access
Status: NEW
: ThinLinc
Web Access
: trunk
: PC Unknown
: P2 Normal
: LowPrio
Assigned To:
:
:
:
: 3523
  Show dependency treegraph
 
Reported: 2013-07-15 17:32 by
Modified: 2019-10-31 11:00 (History)
Acceptance Criteria:


Attachments


Note

You need to log in before you can comment on or make changes to this bug.


Description From cendio 2013-07-15 17:32:50
+----------------+---------------------------+
| Platform       | Fedora 18                 |
+----------------+---------------------------+
| Browser        | Chrome 28.0.1500.89 beta  |
+----------------+---------------------------+

When running the HTML5 client in Chrome key combinations like Ctrl-N and Ctrl-T
are intercepted by the browser and therefor not let through to the remote
session. The intended behavior should be that no browser keyboard shortcuts are
intercepted or that there is an option for intercepting them.

There is a test called input.html in noVNC which was useful. It works fine in
Firefox.
------- Comment #1 From cendio 2016-04-01 14:17:58 -------
If you normally use Ctrl-W while editing text for example, this bug is very
irritating since it results in Chrome closing the tab with the HTML5 client..

See the two links below for some discussion on the topic:
https://bugs.chromium.org/p/chromium/issues/detail?id=33056
https://bugs.chromium.org/p/chromium/issues/detail?id=119881
------- Comment #2 From cendio 2016-04-01 14:23:53 -------
If there is any good way to detect this behavior we could consider adding
buttons, when needed, in the GUI for key combinations like these. For example
like how the Ctrl, Alt, Tab and Esc buttons are presented on touch devices with
low resolutions.
------- Comment #3 From cendio 2016-10-13 16:15:47 -------
This happens in Firefox as well now, so either we or Firefox have changed
something.
------- Comment #5 From cendio 2018-03-06 14:10:05 -------
Wohoo! This now works in Chrome as long as you are in fullscreen! Tested with
Chrome 64 on Linux. Their bug entry states that it was fixed in Chrome 60 (59
for Linux and Windows). Note that F11 doesn't work in fullscreen though as that
is how you go back to windowed mode.

So this is now very similar to how our native client behaves.
------- Comment #6 From cendio 2018-03-06 14:11:24 -------
Note that keys grabbed by the OS are still lost to us (e.g. the Windows key).
------- Comment #7 From cendio 2019-10-31 11:00:57 -------
(In reply to comment #6)
> Note that keys grabbed by the OS are still lost to us (e.g. the Windows key).

Moved this to bug 7414.