New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 733710 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Last visit 21 days ago
Closed: Jul 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug

Blocking:
issue 718037



Sign in to add a comment

Better support for Windows virtual keyboard detection

Project Member Reported by est...@chromium.org, Jun 15 2017

Issue description

A couple features depend on LocationBarView::IsVirtualKeyboardVisible[1] but that only works for the ash virtual keyboard. We need to extend it to work for the Windows one as well. It seems there's code to detect it in ui/base/win/osk_display_manager.cc but it currently just allows listening for showing (which is async) and hiding, rather than statically checking whether a keyboard is visible.

[1] https://cs.chromium.org/chromium/src/chrome/browser/ui/views/location_bar/location_bar_view.cc?rcl=2ec4013ac56a7f30db385949269adc21ae980bf3&l=743
 

Comment 1 by est...@chromium.org, Jun 15 2017

Blocking: 718037
Owner: girard@chromium.org
Status: Started (was: Available)
Patch is at https://codereview.chromium.org/2971363002

Comment 4 by girard@chromium.org, Jul 20 2017

Labels: Proj-TabletChrome-Phase2
Status: Fixed (was: Started)
This can be tested by testing  issue 718037  on Windows devices. Check that the "clear all" button appears while you're typing in the omnibox with the virtual keyboard (and that it doesn't appear if the osk is not shown.)

Sign in to add a comment