Bugzilla – Full Text Bug Listing
|Summary:||On-screen keyboard disappears when interacting with the Web Access GUI|
|Product:||ThinLinc||Reporter:||Karl Mikaelsson <firstname.lastname@example.org>|
|Component:||Web Access||Assignee:||Pierre Ossman <email@example.com>|
|Status:||CLOSED FIXED||QA Contact:||Bugzilla mail exporter <firstname.lastname@example.org>|
|Priority:||P2||CC:||email@example.com, firstname.lastname@example.org, email@example.com|
|Version:||trunk||Keywords:||derfian_tester, focus_focus, prosaic, upstream|
|Bug Depends on:|
Clicking buttons in the GUI makes the on-screen keyboard disappear, triggering a session resize. Discovered on Android 5.1.1/Google Chrome, but I got the feeling this wasn't device-specific from what Pierre/Samuel said.
This problems comes from shitty focus handling in general between the canvas and the UI elements. Fixing this has a high chance of fixing bug 6055 as well.
(In reply to comment #3) > Fixed in upstream noVNC. See https://github.com/novnc/noVNC/pull/697
Pressing "Clear" in the clipboard window when the keyboard is visible makes the keyboard disappear. Verified on Chromebook (Google Chrome) and Android (Google Chrome and Firefox).
(In reply to comment #7) > Pressing "Clear" in the clipboard window when the keyboard is visible makes the > keyboard disappear. Verified on Chromebook (Google Chrome) and Android (Google > Chrome and Firefox). You can now click clear without the keyboard disappearing.
Testing on Windows Touch reveals that Chrome still has this problem: - activate special key control bar - open keyboard - press Ctrl or Alt (other keys hidden by keyboard) - keyboard closes
(In reply to comment #10) > Testing on Windows Touch reveals that Chrome still has this problem: > - activate special key control bar > - open keyboard > - press Ctrl or Alt (other keys hidden by keyboard) > - keyboard closes I can not reproduce using these instructions. It works fine, the keyboard stays open after clicking Ctrl or any other button in the control bar. Tested using Chrome, FF, IE and Edge on Windows 10 touch, also tested Chrome on Chromebook and can't see the issue anywhere. One related issue that could perhaps be what was initially seen here has been noted on bug 6348 however.