Thanks for filing the issue!

Tried checking the issue on reported chrome version 68.0.3440.75 using Windows 10 (Surface Pro) with the below mentioned steps.
1. Launched Chrome
2. Detached the Keyboard-> Clicked/touched on Omni box.
3. Re-attached the keyboard after the on screen keyboard poped up.
4. Tried giving inputs through keyboard.
When the on-screen keyboard is opened we couldn't give any inputs through the hard keyboard, till the on-screen key board disappeared.

@Reporter: Similar behaviour is seen in 67.0.3396.79 where it is mentioned as working and in M60(60.0.3112.0) version too, we couldn't give any inputs through hard keyboard while the on-screen key board is active. Could you please let us know if the process followed is correct i.e., detaching/attaching the keyboard in order to see on-screen key board. Any further inputs from your end may be helpful.

+dtapuska who worked on Windows OSK.

I have also see this issue, but only occurs when Surface is docked to surface dock.

 Issue 871061  has been merged into this issue.

Hey all,

We're seeing a fair amount of user reports about this behavior.

Listnr: 
- https://listnr.corp.google.com/report/85592929393
- https://listnr.corp.google.com/report/85592924753
- https://listnr.corp.google.com/report/85592884749
- https://listnr.corp.google.com/report/85592857240
- https://listnr.corp.google.com/report/85592778036
- https://listnr.corp.google.com/report/85592729602
- https://listnr.corp.google.com/report/85592652439
- https://listnr.corp.google.com/report/85592363668


Community:
- https://productforums.google.com/forum/#!topic/chrome/iTQ4oGpFtfY

Thanks!

nzolghadr@, lanwei@ FYI...

Are these devices running in Tablet mode in Windows 10? We started using a standard windows API to let it determine when the keyboard should be shown or not.

If a physical keyboard is connected the virtual keyboard will appear if you are in tablet mode which is consistent with the rest of the UX on Windows 10 (including Edge).

+Mano@ - can we try recreating this issue?

Yeah, looking into it.

 Issue 871756  has been merged into this issue.

As of now, i'm not seeing this issue on Win10 Pro for latest M68 stable# 68.0.3440.106. Could some one please confirm this issue is specific to a touch device connected to docking station?

Thank you!

Knowing the specific Windows 10 verions could also indicate a trend.

Specifically the new virtual keyboard code is activated for Windows 10 RS4 and later. 1803 and later. This code is more reliable than previous mechanisms.

Adding to #9 - I think this may be the case here instead of a bug.

I can reproduce the behavior of the virtual keyboard popping up unexpectedly on a Surface Go device by:

1) Open Chrome
2) Disconnect Surface keyboard
3) Attach a USB keyboard
4) Touch an entry field in Chrome
5) Virtual keyboard appears

This also happens in Edge though, so it isn't Chrome-specific. I think the device is still technically in Tablet mode even though it's "docked" to a USB keyboard and mouse.

If logs or the sort are useful from the repro above, let me know.

What is your Windows 10 version? In RS4 and later we are deferring to the OS to handle this. Before we had some hacky logic and Microsoft added this API to be consistent. Since this is done in Edge as well and since you are in tablet mode then this is expected, so likely this needs a ticket for Microsoft to address.

I'm running Windows 10 Home, Version 1803, Build 17134.191.

Gotcha - and agreed. It sounds like this may simply be expected behavior from using the API.

Thanks for the help debugging and ruling out a Chrome-specific issue!

Thanks - based on this discussion above, removing RBS label for now. Let's add it back if needed. 

dtapuska@ - do you know who can help create the ticket for Microsoft?

Are there any workaround solutions we can provide to users?

On my Surface Pro 3, I also have this issue - I'm running Windows 8.1, with USB mouse & keyboard, Chrome Version 68.0.3440.106 (Official Build) (64-bit).

Whenever I click onto any field to type, the virtual keyboard pops up even when my keyboard is plugged in. 

This seems to only happen in Chrome, this doesn't happen in Firefox. 

#19: Thanks for chiming in! Can you test in Edge as well and see if the virtual keyboard appears there? We believe it will from our testing. Thanks!

#20 Windows 8.1 doesn't have Edge, that was only introduced in Win10.

#20: This bug is more in line with  Issue 871756  than the original bug reported here. This issue deals with a virtual keyboard blocking physical keyboard input in the address bar on Windows 10 machines, while  Issue 871756  deals with a touch keyboard appearing on Windows 8.1 machines whenever a text area is selected, but not blocking input from a physical keyboard. Can you un-merge these issues, as they address separate issues?

Thank you!

#22: The bug reported in #19, that is. I apologize for the ambiguity.

#21/22/23: Thanks!

@dtapuska Could you take a look at  bug 871756  and see if this is the same root cause? That behavior seems specific to Windows 8.1, and I'm not sure if we should expect the new behavior on pre-10 systems. Thanks!

It would not be the same root cause because the API doesn't exist on Windows 8.1.  Unfortunately I don't have any Windows 8.1 devices to quickly test this out. I'll have to defer to nzolghadr@ to investigate these. 

@dtapuska Thanks! I've un-duped the other bug for now.

I am seeing similar, Surface Pro on Windows 10 using a USB keyboard & mouse, any input fields (or address bar) on Chrome displays the on screen keyboard, it doesn't block input from physical keyboard and as soon as input is entered on physical keyboard, the on screen one goes away. 

Doesn't happen in any other apps and specifically does not happen in Firefox or Edge. 

We have multiple models of devices experiencing this same issue of OSK popping up even when confirmed not in Tablet mode. We have had reports by users using Surface Pro and Lenovo Twist, all touch screens. Some with different Windows 10 versions, all only happening when using Chrome. Edge, IE, and Firefox do not have this issue.

We have tried multiple solutions that have not fixed the issue.

Just to give you an update about this issue. Chrome has bunch of heuristics on when to show the virtual keyboard. It mainly comes down to the type of the hardware and whether it is capable of having physical keyboard or wether something is attached to it already.

It seems that those heuristics just made thing complicated as oppose to a simple model that we believe Firefox, Edge, and other Windows UI follow. The new model we are going to follow is to always show VK with touch and never show it when it is with mouse/keyboard. This makes it consistent with behaviors in other apps as far as we found.

@nzolghadr,

Do you have any estimate of when this will be fixed/implemented? Additionally, you merged this issue into   Issue 871756  , but I don't know if they are the same issue. In C#25, it states that "It would not be the same root cause because the API doesn't exist on Windows 8.1." Has the API been ruled out as the cause? Also, this issue deals with the blocking of physical keyboard input as a result of the touch keyboard appearing, while   Issue 871756   does not. All this to say: I don't know if these bugs are duplicates. Thank you for your help!

We are changing the behavior to make it simple and predictable across the versions. The code is being reviewed at this point. So it is going to make it to M70.

#32 This code also fixes the  Issue 871756 ?