Bugzilla – Bug 5547
Web Access fails to notice a keyboard close on Android and touch-mode Windows
Last modified: 2019-09-02 16:43:07
You need to
before you can comment on or make changes to this bug.
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.
*** Bug 6060 has been marked as a duplicate of this bug. ***
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
None of the browsers on iOS have this problem. This is a problem on Android and
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.
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
There is a new standard that is supposed to address this: