Bug 5547 - Web Access fails to notice a keyboard close
Summary: Web Access fails to notice a keyboard close
Status: NEW
Alias: None
Product: ThinLinc
Classification: Unclassified
Component: Web Access (show other bugs)
Version: pre-1.0
Hardware: PC Unknown
: P2 Normal
Target Milestone: LowPrio
Assignee: Samuel Mannehed
Keywords: focus_focus
: 6060 (view as bug list)
Depends on:
Reported: 2015-05-22 08:36 CEST by Pierre Ossman
Modified: 2022-12-16 14:38 CET (History)
3 users (show)

See Also:
Acceptance Criteria:


Description Pierre Ossman cendio 2015-05-22 08:36:01 CEST
If you close the keyboard on Android using the system UI rather than our button, then we fail to notice this and think the keyboard is still up. Besides an incorrect looking UI, we also get a bit confused and the keyboard pops up again on some unrelated actions.

Seen with both Chrome and Firefox on Android.
Comment 1 Samuel Mannehed cendio 2016-10-18 15:01:54 CEST
*** Bug 6060 has been marked as a duplicate of this bug. ***
Comment 2 Samuel Mannehed cendio 2016-10-18 15:03:21 CEST
From bug 6060:

> 1. Bring up the keyboard by pressing the keyboard button.
> 2. Close the keyboard from the keyboard itself, ie press the device back button
> Now, the keyboard button is still highlighted, and the code still believes that
> the keyboard is active/visible. If you press the button again, the button will
> be longer be highlighted, but nothing else happens, because the keyboard was
> already hidden. 
> As far as we know, fixing this is difficult since it is not possible to
> determine if the keyboard is visible or not. Instead, my suggestion is to
> change the button from "toggle keyboard" to "activate keyboard". The code would
> need to re-set focus to the input field so that the keyboard is visible for
> sure.
Comment 3 Samuel Mannehed cendio 2016-10-18 15:04:23 CEST
None of the browsers on iOS have this problem. This is a problem on Android and
Windows mobile.
Comment 4 Thomas Nilefalk cendio 2017-04-19 15:17:55 CEST
On Windows Touch, Firefox, Chrome and IE does not notice the close but a press on the indicator only turns it off, so it's back in sync.

Edge does not notice the close either, but a press on the indicator immediately opens the keyboard again, which might be considered worse.
Comment 5 Samuel Mannehed cendio 2017-04-24 16:57:16 CEST
This bug is about the Web Access interface not noticing when the keyboard is closed by means outside of our interface. Note bug 6348 about our interface button itself not working.

Also note that Chrome on Chromebook seem to work exactly like the browsers on Android here.
Comment 6 Pierre Ossman cendio 2019-09-02 16:43:07 CEST
There is a new standard that is supposed to address this:

Comment 7 Frida cendio 2022-11-29 15:46:42 CET
This is also now an issue in iOS, tested on iPadOS 15.7.1 with Edge 107 and Safari.
Comment 8 Frida cendio 2022-12-05 11:31:40 CET
(In reply to Frida from comment #7)
> This is also now an issue in iOS, tested on iPadOS 15.7.1 with Edge 107 and
> Safari.

1. Open keyboard using Web Access sidebar
2. Close keyboard using the native keyboard-down symbol
3. Press "Extra keys" in sidebar

This results in both keyboard and extra keys to be selected, although the keyboard was down. To open the keyboard again, I had to click twice.

Another way to test this is to open the keyboard then opening a new tab, this will close the keyboard, then go back to the Web Access tab. Web Access still thinks the keyboard is up.

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