Virtual keyboard takes up half the screen in portrait rotation on touchscreen convertible Chromebooks.
Reported by
0spor...@gmail.com,
May 2 2016
|
|||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; CrOS x86_64 7834.70.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/49.0.2623.112 Safari/537.36 Steps to reproduce the problem: 1. Flip Chromebook into tablet position. 2. Tap on text box to bring up onscreen keyboard. 3. What is the expected behavior? That it wouldn't take up this much space. What went wrong? Touch compatibility does not exactly mean everything needs to be bigger. The accessibility onscreen keyboard isn't that big. If anything, the size for the virtual keyboard should fall just between the current size and the size of the accessibility onscreen keyboard. Did this work before? N/A Chrome version: 49.0.2623.112 Channel: stable OS Version: 7834.70.0 Flash Version: Shockwave Flash 21.0 r0 #CBC-RS/TC-watchlist Tested on the Acer C738T and the Lenovo Thinkpad 11e.
,
May 13 2016
,
Jun 18 2016
Acer Chromebook R11. This makes tablet mode quite frustrating to use.
,
Jul 29 2017
,
Aug 1 2017
We are looking into ways to resolve this.
,
Aug 2 2017
Thanks, glad to see that it's being looked into. Another step towards improving tablet mode for convertible ChromeOS devices.
,
Jun 4 2018
(Bulk Edit) Adding the new conops Chrome OS hotlist to all open issues with the "#CBC-RS/TC-watchlist" tag, our former tracking tag.
,
Jul 4
Is this still a problem if we have the floating keyboard?
,
Jul 12
The floating keyboard should help here, as long as user's selection to use it is sticky. It really begs the question though of whether we just have a single keyboard with size & placement options.
,
Jul 26
I have no idea if it would be possible, and it would probably be a lot of work, and maybe I should create a separate feature request, but I'm just going to throw my idea out there: It would be really awesome if I could use any old Android keyboard as my input method. The advantage to this approach would be that I instantly get all or many of the awesome features that exist in the Android ecosystem. The downside is the probably huge complexity involved in shuttling keyboard activity between the Android environment and the host ChromeOS environment. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by dymp...@gmail.com
, May 3 2016110 KB
110 KB View Download