New issue
Advanced search Search tips

Issue 746492 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner: ----
Closed: Aug 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 1
Type: Bug



Sign in to add a comment

Location bar doesn't trigger keyboard when selected with Win10 stylus.

Project Member Reported by pbos@chromium.org, Jul 19 2017

Issue description

Chrome Version: 59.0.3071.115 (Official Build) (64-bit) (cohort: Stable)
OS: Win10

What steps will reproduce the problem?
(1) Use Surface Pro 4 tablet stylus to navigate.
(2) Click location bar

What is the expected result?

On-screen keyboard shows up so you can type.

What happens instead?

Location bar gets selected, but since you don't have a keyboard plugged in you can't type.

Please use labels and text to provide additional information.

Touching other text fields with the stylus inside Chrome (text box in Hangouts chat for instance) do trigger text entry, just not the location bar.

Tapping the location bar with your fingers make the on-screen show up, but the stylus doesn't.
 

Comment 1 by mustaq@chromium.org, Jul 20 2017

Cc: dtapu...@chromium.org
Components: -UI>Input>Text Blink>Input
Labels: -Pri-3 Hotlist-Input-Dev Pri-1
Status: Available (was: Untriaged)

Comment 2 by mustaq@chromium.org, Jul 20 2017

I tried on beta (M60): the keyboard doesn't show up even with touch!  Edge works perfectly.

Few observations:
- A hovering stylus on the address bar shows a text cursor in Chrome, but a pointer cursor in Edge.
- Right after Chrome starts, a stylus tap on the address bar briefly shows a "waiting" cursor but a touch tap shows a touch handle as if a long tap has been done.

Comment 3 by pbos@chromium.org, Jul 20 2017

In my setup it shows up with touch but not with the stylus. It's a Surface Pro 4 with Windows 10, x64. Chrome Version: 59.0.3071.115 (Official Build) (64-bit) (cohort: Stable) as mentioned above. I can try on any other tracks if handy, I just haven't moved over to dev there yet.
Status: Fixed (was: Available)
This is fixed with the fix for  issue 746581 

Sign in to add a comment