Keyboard doesn't show up on 1GiB Android Go device |
|||
Issue description"gobo" device running OMB1.171211.001. Chrome Home is enabled in chrome://flags. Monochrome (set as webview provider) at ToT (af82ecb2140cc0cdac91c40c476120864fb03ab1). Closing a tab and clicking the omnibox summons blinking cursor, but no keyboard shows up. Keyboard is not killed by OOM killer, there are no "LatinIme" logcat messages (I can see them when it does show up), so it appears that Chrome simply doesn't trigger it.
,
Dec 14 2017
This has something to do with low-end tab switcher. I can't repro the issue if I disable low-end mode with --disable-low-end-device-mode.
,
Dec 27 2017
I've reproduced it on Google Pixel and Pixel 2 Both stable Chrome 63.0.3239.111 and Chrome Beta New "home" ui Steps: 1) Open omnibox 2) Click on any site icon (youtube or wikipedia, for example) 3) Click on search field May be somehow related to Android 8.* - both devices running on it
,
Feb 7 2018
,
Feb 8 2018
Is this happening only when Chrome Home is enabled?
,
Feb 8 2018
Yes - please ignore my comment #1. We're doing this through UiUtils.showKeyboard() which didn't show in search results when I searched for showSoftInput().
,
Feb 13 2018
With the Chrome Home experiments ramping down, this is obsolete. |
|||
►
Sign in to add a comment |
|||
Comment 1 by changwan@chromium.org
, Dec 14 2017