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

Issue 821318 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner:
Closed: Sep 12
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

Non-Regression:On-Screen keyboard doesn't get popped-up immediately when cursor is at Name field of Add printer overlay

Project Member Reported by rkalavakuntla@chromium.org, Mar 13 2018

Issue description

Chrome Version:65.0.3325.159/10323.55.0 Beta channel Daisy,Kip,Reks
OS:Chrome OS

What steps will reproduce the problem?
(1)Sign into user ->Enable 'On-Screen Keyboard' from Accessibility settings
(2)Go to chrome://settings/cupsPrinters page ->click to Add Printer and Observe

Expected:When Add Printer overlay is opened,On-Screen keyboard should popped-up immediately since default cursor is at Name field 
Actual:Instead,On-Screen keyboard doesn't get popped-up when cursor is at Name field


This is a Non-Regression issue seen from M-62

Note:
1.Issue is not seen in Linux,Windows OS
2.Issue is also seen on latest M-67 dev




 


 
Actual.mp4
7.5 MB View Download
Shouldn't on-screen keyboard only pop up when user taps the touch input?
Owner: iloahz@chromium.org
Hi rkalavakuntla,

The issue looks like something when triggering onFocus callback.

I just checked 10557 on link, the issue didn't repro, can you take another look on 10557 or above?

Thanks!
Status: Started (was: Untriaged)
Able to reproduce the issue on 67.0.3390.0/10559.0.0 dev channel Cyan.
Attached the screencast for reference..
Thanks!
821318.mp4
10.3 MB View Download

Comment 6 by iloahz@chromium.org, Apr 10 2018

thanks for the quick response.

i did another test on bob, the issue also didn't repro, i'll try find one cyan.

Comment 7 by iloahz@chromium.org, Apr 11 2018

Status: Assigned (was: Started)
This bug has a target milestone that has passed.  Please help bug cleanup: mark it closed or update/remove the milestone target. 
Labels: -M-65 M-70
Reproed on latested Link, will try to fix in later version.
Owner: shend@chromium.org
Status: WontFix (was: Assigned)
Usually, the virtual keyboard only shows up from a user gesture (e.g. by clicking the text field, by clicking a button that causes an input to be focused). See the discussion in 642513.

Based on the discussion in 642513, it looks like this is WAI. We shouldn't be automatically showing the VK when navigating to a new page (in this case it's a modal dialog, but same idea).

From a UX perspective, I guess it's better for users to see the entire form first before forcing them to start entering information?

Sign in to add a comment