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

Issue 892709 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 491516
Owner: ----
Closed: Oct 16
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

The on-screen keyboard sometimes will not appear when it should when using Chrome on a Microsoft Surface Pro with the physical keyboard detached

Reported by robin.bl...@gmail.com, Oct 5

Issue description

UserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3497.100 Safari/537.36

Example URL:

Steps to reproduce the problem:
1. Launch Chrome.
2. Go to a page that has a text area or text input control (such as www.google.com, translate.google.com, stackoverflow.com).
3. Click the plus (+) button to open a new tab.
4. Go back to the tab that was used to open the page that was opened in step 2.
5. Tap in the text control on the page.

What is the expected behavior?
The on-screen keyboard will appear.

What went wrong?
The on-screen keyboard does not appear.

Does it occur on multiple sites: Yes

Is it a problem with a plugin? No 

Did this work before? N/A 

Does this work in other browsers? Yes

Chrome version: 69.0.3497.100  Channel: stable
OS Version: Windows 10 Professional (Version 1803 - 10.0.17134)
Flash Version: 

It is not just opening a new tab that can trigger this problem. Even opening and closing another Windows application can trigger it. It is almost as if
anything that takes focus off the page will cause the on-screen keyboard to no longer pop up automatically for that page.

Note that tapping in the address bar (which WILL bring up the on-screen keyboard) seems to "fix" the issue, at least temporarily until something takes focus away from the page again.
 
Components: -Blink UI>Input>VirtualKeyboard
Don't have a Surface Pro to test with.  Setting component for further triage.
Labels: Needs-Triage-M69
Labels: Triaged-ET
Mergedinto: 491516
Status: Duplicate (was: Unconfirmed)
The issue looks similar to issue id: 491516. Hence, merging into the issue id: 491516.
Please feel free to undupe the same if not the case.

Thanks...!!

Sign in to add a comment