Bug 7388 - keyboard stops working on Chrome on Android
Summary: keyboard stops working on Chrome on Android
Status: CLOSED WORKSFORME
Alias: None
Product: ThinLinc
Classification: Unclassified
Component: Web Access (show other bugs)
Version: trunk
Hardware: PC Unknown
: P2 Normal
Target Milestone: 4.11.0
Assignee: Bugzilla mail exporter
URL:
Keywords:
Depends on: 7365
Blocks:
  Show dependency treegraph
 
Reported: 2019-10-08 10:45 CEST by Pierre Ossman
Modified: 2019-10-31 12:57 CET (History)
1 user (show)

See Also:
Acceptance Criteria:


Attachments

Description Pierre Ossman cendio 2019-10-08 10:45:08 CEST
Upstream found an issue where the hidden input field can lose focus when the display is clicked, at which point keyboard input would stop working.

As far as I remember only Chrome on Android uses the hidden input field, so it should be the only thing affected by this.

Upstream fix here:

https://github.com/novnc/noVNC/commit/1d6ff4a

We need to see if we can provoke this bug and see if the updated noVNC indeed avoids the issue.
Comment 1 Alex Tanskanen cendio 2019-10-31 11:31:14 CET
I tried to reproduce the bug on eudemo by doing the following: 

1. Typing in some text field
2. Close the keyboard
3. Click the display that isn't a part of the text field
4. Open the keyboard and start typing
5. Observe that no text appears

If I reproduce this on the latest build the same behavior doesn't exist. This probably means that this was the problem, which is now fixed.
Comment 2 Alex Tanskanen cendio 2019-10-31 12:56:14 CET
(In reply to comment #1)
> 
> 1. Typing in some text field
> 2. Close the keyboard
> 3. Click the display that isn't a part of the text field
> 4. Open the keyboard and start typing
> 5. Observe that no text appears
> 

This cannot be reproduced every time and this is was probably a different problem in upstream which is now also fixed. 



> https://github.com/novnc/noVNC/commit/1d6ff4a

What they described here is irrelevant for webaccess since upstream featured a version which we never used.

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