VR Omnibox: Keyboard disappears if user clicks in thin space between omnibox and first result |
|||||||
Issue descriptionChrome Version: 65.0.3316.0 OS: Android N VrCore: 1.12.177372015 What steps will reproduce the problem? 1. Enter VR 2. Click URL area in omnibox to switch to “omnibox text entry mode” 3. type some text 4. click in thin space between omnibox and first suggestion above it. What is the expected result? nothing What happens instead? keyboard disappears. See screenshot.
,
Jan 18 2018
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/fbb1613b7b4ed4597cf5b841cbcd4b77e1fb73dd commit fbb1613b7b4ed4597cf5b841cbcd4b77e1fb73dd Author: Yash Malik <ymalik@google.com> Date: Thu Jan 18 17:46:36 2018 VR: Show keyboard when cancelling audio permission prompt Also make the spacer in the suggestions layout and the back button non-focusable so it doesn't steal focus from the omnibox and hide the keyboard. Bug: 801402 , 801634 Cq-Include-Trybots: master.tryserver.chromium.android:android_optional_gpu_tests_rel;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel Change-Id: Ia7b09b66e7f98ddc89ede4f67a4ad02544079553 Reviewed-on: https://chromium-review.googlesource.com/871515 Reviewed-by: Christopher Grant <cjgrant@chromium.org> Commit-Queue: Yash Malik <ymalik@chromium.org> Cr-Commit-Position: refs/heads/master@{#530189} [modify] https://crrev.com/fbb1613b7b4ed4597cf5b841cbcd4b77e1fb73dd/chrome/browser/vr/elements/button.cc [modify] https://crrev.com/fbb1613b7b4ed4597cf5b841cbcd4b77e1fb73dd/chrome/browser/vr/elements/text_input.cc [modify] https://crrev.com/fbb1613b7b4ed4597cf5b841cbcd4b77e1fb73dd/chrome/browser/vr/ui_scene_creator.cc
,
Jan 18 2018
,
Feb 8 2018
,
Feb 14 2018
This still repros in build 66.0.3346.0 Canary build on a Pixel 2 Android 8.1.0
,
Feb 26 2018
,
Apr 23 2018
Hi Chris, sending this your way :)
,
Apr 23 2018
This is obsolete and no longer an issue. An omnibox layout refactor CL inadvertently fixed this issue. |
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by offenwanger@chromium.org
, Jan 12 2018Status: Assigned (was: Untriaged)