Issue metadata
Sign in to add a comment
|
Virtual keyboard not responding - Kiosk mode - AOpen Chromebase
Reported by
markwar...@bannatyne.co.uk,
Feb 2 2018
|
||||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.132 Safari/537.36 Platform: 10032.86.0 (Official Build) stable-channel sumo Steps to reproduce the problem: 1. Launch Chrome in Kiosk mode 2. Attempt to tap into text box 3. Unable to type 4. Plug mouse into Chromebase 5. Attempt to tap into text box 3. Able to type What is the expected behavior? Without mouse plugged into Chromebase, users able to tap and enter text What went wrong? Chromebase Aopen WT22M-FBG - Virtual Keyboard not responding (Kiosk mode / iframe) The issue is around the virtual keyboard not responding when selecting input boxes on webpages that are contained in an iframe If we add a mouse it allows the keyboard to appear. So unless a mouse is plugged in it will not allow you to tap into a text box and type on the pop up keyboard. We had this issue previously when we went over version 50 however this was resolved when we were advised to try version 59. Not fully sure when this broke again following v59 (think around beginning of November) but now on v63 we are experiencing the same problem. Thanks Did this work before? Yes v59 (maybe later) Chrome version: 63.0.3239.140 Channel: stable OS Version: 63.0.3239.140 Flash Version: Google_Sumo.5216.382.5
,
Feb 22 2018
This issue looks like a duplicate of issue 779968 . Could you try the workaround described in comment 3 in crbug.com/799970 ? |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by xiy...@chromium.org
, Feb 2 2018