Thanks for filing the issue!

Unable to reproduce the issue on reported chrome version 68.0.3440.84 using window 10(Surface Pro) with the below mentioned steps.
1. Launched Chrome
2. Connected Keyboard and external mouse
3. Clicked on an input field using mouse and also with "tab" key.
When the input field/text area is made active using mouse/tab key we didn't observe any onscreen keyboard.

@Reporter: Could you please let us know if the same issue is seen across other browsers and is that specific to OS version mentioned in C#0. As we do not have Windows 8.1 touch screen with us couldn't test in the mentioned OS. Could you please check the same on a new profile without any apps & extensions and let us know if the issue persists.

I also have 7 windows 8.1 surfaces that are exhibiting the same issue. 

They have external keyboards and mice connected. 
Clicking in a field with tab or the mouse causes the same error. 
We tested IE and Firefox as well the issue only occurs in chrome. 
This was working fine before the 68.0.440.84 update. 

vamshi.kommuri,

I have run Chrome in Guest Mode, and it had the same issue with both the mouse and keyboard. 
This issue is specific to Chrome (I tested the same input patterns in Firefox and did not trigger the touch keyboard). 
Also: if this helps, I found a report of the same issue on the Google Product forums: https://productforums.google.com/forum/#!topic/chrome/KOAgg2L-GsA

Thank you for your help.

Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

 Issue 872326  has been merged into this issue.

 Issue 872301  has been merged into this issue.

Tried checking the issue using Surface Pro Windows 10 by connecting an external wired keyboard on chrome versions 68.0.3440.84, 70.0.3516.0 and on 60.0.3112.0.

Our Observations:
-------------------
When external keyboard is connected, on touching input field On-screen keyboard is seen. Up on clicking Ctrl+Tab keys a new tab is opened, along with a NTP an On screen keyboard is also seen. This issue is seen from M60(60.0.3112.0). Attaching the screen cast of the same for reference.
Note: Couldn't connect both Keyboard and mouse at once as only single USB port is available.

@Reporter: Could you please have a look at the screen cast and let us know if the issue is seen in 60.0.3112.0 from attached video. Any further inputs from your end may be helpful.

Thanks!

Deleted: 871756.mp4 1.5 MB

	871756.mp4 1.5 MB View Download

I have a Microsoft Surface Pro 3 running Windows 8.1 and I use a USB mouse and keyboard. I'm running the latest version of Chrome (it auto updates for me, version 68 I believe). I am also experiencing this issue where the virtual keyboard comes up whenever you click on a text input field in Chrome -- this is when I have my USB keyboard/mouse connected. 

This appears to be a duplicate of  bug 868264 .

Craig Tumblison: This bug does not prevent keyboard input, and is therefore not a duplicate of  bug 868264 . 

Vamshi Kommuri:
The video does not seem to be a replication of the issue reported. When I open a new tab with CTRL-T or clicking the mouse on the new tab button, that is actually the one of the few times (perhaps the only time) that the touch keyboard does not pop up. The touch keyboard appears only when I use the mouse or keyboard to directly select a text area (so opening a new tab does not trigger it, but clicking the omnibox once I do so does trigger it). However, resizing text boxes (such as this comment box) does seem to trigger the bug.

Thank you for your help.

Marking as non-dupe as this appears to be separate behavior from  bug 868264 .

Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

This bug will make many people to switch over to edge , only way while chrome fixes the issue is this  https://support.microsoft.com/en-us/help/4028019/windows-enable-and-disable-your-touchscreen-in-windows-10

#15: As this is a Windows 8.1 issue - not a Windows 10 issue - users cannot switch to Edge (A Windows 10 program).

In Windows 8.1, I have an ASUS T100, with an attached keyboard/mouse. Original post described my problem exactly. This problem began as soon as I updated to the most recent version.

Hi everyone

I'm coming from the Spanish Chrome Help Forum and there are some cases similar to this report.

The users told us that the issue happens both in Windows 8.1 and 10, but that this problem started in the last version of Chrome and they confirmed that this only happens in Chrome.

Some users also told us that deactivating the touch keyboard didn't help, except one user that said that this worked (He has a Lenovo Twist).

All the rest of the details are the same published on this report.

 Issue 873793  has been merged into this issue.

Unable to reproduce the issue on using Surface Pro Windows 10 by connecting an external wired keyboard on reported chrome version 68.0.3440.84 and latest cheome #70.0.3521.0. Routing to inhouse team to check the issue on Windows 8.1 as the issue is not getting reproduced on Windows 10, by following below steps.

Steps:
=====
1.Launched chrome.
2.Connected an external keyboard to Surface pro.
3.Opened www.facebook.com.
4.By using the tab button on the external keyboard navigated to the textboxes, observed that Windows touchpad did not appear on the screen. 
Note: Tried the same process by connecting external mouse also, but unable to reproduce the issue.

Attached screencast for reference.

Thanks.!

Deleted: 871756(1).mp4 2.4 MB

	871756(1).mp4 2.4 MB View Download

#20: This version of the bug (or at least this report) is exclusively Windows 8.1. There is a similar issue with Windows 10 ( Issue 868264 ), and this video would probably help them more than it can help this issue. Thank you for your help. 

@All future testers: This specific issue must be tested on Windows 8.1 to replicate it, not Windows 10. The Windows 10 issue is slightly different and has been confirmed to not share the same root cause.  Issue 868264  is the Windows 10 version of the bug, and all tests of that bug should be submitted there. Thank you for your help!

Tested this issue on Windows 8.1(Lenova ThinkPad) with chrome #68.0.3440.84; #68.0.3440.106 as per steps mentioned in the comment #0 and didn't observe any on-screen-keyboard while clicking on the omnibox or text area.

Attaching the screen-cast for reference.

Since Windows Surface Pro machine is not available with TE team,hence adding TE-Hardware-Dependency label

I have a client the experiencing this issue.

They are running a Lenovo Thinkpad Twist (33476UU).  This is a laptop with a keyboard that twists 180 degrees so the device becomes essentially a tablet.  So in twisted mode the keyboard is deactivated.  It is running Windows 8.1 build 9600.

Since upgrade to Chrome 68 (68.0.3440.106), and while in normal laptop mode, an onscreen keyboard pops up when clicking on any and every text field. This has made Chrome unusable.

I think the key to this bug is having a keyboard that can be disabled through some internal software function.

@Comment 23,

This is true in my case - I have a laptop that can convert to tablet mode. While in laptop mode, using the keyboard/mouse, anytime I click in a text box or tab to another text-entry field, the onscreen keyboard pops up. 

The only way I have found to get around it is to disable the onscreen keyboard altogether (via Services), which makes my tablet mode useless.

Please see screenshot.

Deleted: snip_20180816084253.png 55.4 KB

	snip_20180816084253.png 55.4 KB View Download

Hey all,

Just confirming that we continue to see user reports of this happening on 8.1.

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

For Windows 10 reports,  bug 868264  has more detail.

Thanks!

Not sure if both are same but looks like root cause is already identified in  Issue 335735 (C#205),Adding Stable blocker here as well to M-68 and M-69 for tracking.

I'm waiting for a hardware to reproduce the issue locally and look into that.

Here is a video sent from a user that reproduces the issue:

https://drive.google.com/file/d/1LhvZzbhpMliK5OC6d-WahXSxWW03pEPb/view

Friendly ping to get an update as stable release is coming soon and this bug is marked as RBS for M68/M69.
Thanks..!

 Issue 875629  has been merged into this issue.

 Issue 335735  has been merged into this issue.

Still waiting for the device to be delivered to reproduce the issue locally on the dev side.

M69 Stable promotion is coming VERY soon. Your bug is labelled as Stable ReleaseBlock, pls make sure to land the fix and request a merge into the release branch ASAP. Merge has to happen latest by 4:00 PM PT Friday (08/24/18) in order to make it to next week stable cut. Thank you.

Likely that base::win::IsKeyboardPresentOnSlate() returns false unexpected.

@nzolghadr, were you able to get the device and repro?  

Not yet. I got the device but it doesn't have a Win8. I'm waiting for the approval to be able to install Win8 on it.
I wasn't personally able to reproduce this on Win10 v1709. I asked Lan and she couldn't reproduce it either. She is also working on getting a Win 8 device which might be faster than my way.

It´s been rounding a workaround in the Chrome Forum that says that activating the "Compatibility mode" of Windows on Chrome solves the issue. The reason why this works for some users is unknown.

M69 Stable promotion is coming VERY soon. Your bug is labelled as Stable ReleaseBlock, pls make sure to land the fix and request a merge into the release branch ASAP. Merge has to happen latest by 1:00 PM PT Tuesday (08/28/18) in order to make it to next week stable cut. Thank you.

#38: I have tried running Chrome in Compatibility Mode on my Windows 8.1 machine for Windows 8 and Windows 7, but it did not resolve the issue. Can you elaborate on how this was attempted/described on the Chrome Forum?

The workaround was given by a user in this post: https://productforums.google.com/forum/#!topic/chrome-es/5Nf7kHtbnjw;context-place=forum/chrome-es (In Spanish)

These are the steps:

2.- Right click on the icon of Google Chrome and select "Properties"
3.- In Google Chrome Properties, go to "Compatibility" and select "Compatibility with Windows 7"
5.- Restart.

As a quote, this workaround only works for a few people. The reasons why this happen, as I mentioned before, is unknown.

M69 Stable promotion is coming VERY soon. Your bug is labelled as Stable ReleaseBlock, pls make sure to land the fix and request a merge into the release branch ASAP. Merge has to happen latest by 1:00 PM PT Tuesday (08/28/18) in order to make it to stable cut tomorrow. Thank you.

Lan is working on a fix. However, the fix is not obvious and too risky for merge into the release branch. We will be working on the fix and testing it on Canary/Dev branches but I suggest following the workarounds for now. Hence removing the stable blocker.

This problem not have a solution?

If the fix is not obvious and too risky, could you please consider reverting the bogus commit that caused this regression?

You can always append the "--disable-usb-keyboard-detect" switch to the command line and it should prevent the keyboard from appearing.

#46:
Forgive me for not knowing, but how does one add the switch to Chrome when running in Windows 8.1? The flag mentioned is not accessible through Chrome Flags as far as I can tell, and I have no almost knowledge of how to use the command line in Windows (Which, admittedly, is not a good thing and I should fix that). In chrome://version, I can see the current flags that I have, but no way to add flags. Thank you for your help.

#47 - You can edit the shortcut (right click on it -> properties) on desktop or you can edit the start bar's docked icon (right click on it -> right click on the bottommost Chrome entry -> properties). Just add it to the target field. I don't think it's possible to edit the flags if you are running Chrome by searching for it by name in the Start fullscreen ui.

That being said, I tried to add that flag, but it doesn't appear to do anything. Bug is still there, flag present or not. I also tried to run the Windows 7 compatibility mode, but Chrome crashes instantly when run under it, so this doesn't seem like a solution :(.

Obviously, disabling the tablet mode completely by trashing the onscreen keyboard service, as suggested in other thread, is not a preferable solution.

For now, I had to switch to Firefox while waiting for a fix

I have ran into a issue with changing chrome to run in windows 7 compatibility mode when a user opens a attachment to a office program like excel in this case from a website on chrome he gets a error Microsoft Office cannot verify the license for this product.You should repair the Office program by using Control Panel. The only way I could fix the issue is to run office programs in windows 8 compatibility. The user has windows 8.1 and latest version of chrome. 

 Issue 868264  has been merged into this issue.

Whats next here ?

Whats next here ?

 Issue 868264  is merged here, and its comments #29 and #32 indicate how the problem will be resolved and that it should appear in M70. 

Has anyone else tried the "--disable-usb-keyboard-detect" switch? It does not fix the issue on the my Win 8.1 Dell Inspiron, so disabling touch screen is still the only short term option.

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/ec60a040ccd62e7eb831fa2d359368bd7bf953a8

commit ec60a040ccd62e7eb831fa2d359368bd7bf953a8
Author: Lan Wei <lanwei@chromium.org>
Date: Tue Sep 11 19:41:33 2018

Do not show virtual keyboard for all mouse inputs

We have an issue that Windows virtual Keyboard appears whenever a text
area is selected with the mouse or keyboard. Since we decide to only
show the virtual keyboard when the input type is touch.

Bug:  871756 
Change-Id: Ia804afad907341ed478409d223b67f09c6b7f8f3
Reviewed-on: https://chromium-review.googlesource.com/1194406
Reviewed-by: Pavel Feldman <pfeldman@chromium.org>
Reviewed-by: Marc Treib <treib@chromium.org>
Reviewed-by: Keigo Oka <oka@chromium.org>
Reviewed-by: Lei Zhang <thestig@chromium.org>
Reviewed-by: Navid Zolghadr <nzolghadr@chromium.org>
Reviewed-by: Sadrul Chowdhury <sadrul@chromium.org>
Commit-Queue: Lan Wei <lanwei@chromium.org>
Cr-Commit-Position: refs/heads/master@{#590440}
[modify] https://crrev.com/ec60a040ccd62e7eb831fa2d359368bd7bf953a8/chrome/browser/renderer_host/site_per_process_text_input_browsertest.cc
[modify] https://crrev.com/ec60a040ccd62e7eb831fa2d359368bd7bf953a8/chrome/browser/ui/search/search_tab_helper.cc
[modify] https://crrev.com/ec60a040ccd62e7eb831fa2d359368bd7bf953a8/content/browser/renderer_host/render_widget_host_view_aura.cc
[modify] https://crrev.com/ec60a040ccd62e7eb831fa2d359368bd7bf953a8/content/browser/renderer_host/render_widget_host_view_aura.h
[modify] https://crrev.com/ec60a040ccd62e7eb831fa2d359368bd7bf953a8/content/browser/renderer_host/render_widget_host_view_aura_unittest.cc
[modify] https://crrev.com/ec60a040ccd62e7eb831fa2d359368bd7bf953a8/content/public/test/text_input_test_utils.cc
[modify] https://crrev.com/ec60a040ccd62e7eb831fa2d359368bd7bf953a8/content/public/test/text_input_test_utils.h
[modify] https://crrev.com/ec60a040ccd62e7eb831fa2d359368bd7bf953a8/ui/views/controls/textfield/textfield.cc

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/ef148a7c5b01a810bd74d49968aaf00f6ff9f4c4

commit ef148a7c5b01a810bd74d49968aaf00f6ff9f4c4
Author: Lan Wei <lanwei@chromium.org>
Date: Wed Sep 12 00:36:53 2018

Setup the observer before calling DisplayVirtualKeyboard

This is a follow up CL of
https://chromium-review.googlesource.com/c/chromium/src/+/1194406

We should setup the keyboard observer before displaying the virtual
keyboard otherwise the observer won't see the change of the virtual
keyboard.

Bug:  871756 
Change-Id: I6b13072ed06d9e10d188c553082b411f2bb09326
Reviewed-on: https://chromium-review.googlesource.com/1220560
Reviewed-by: Sadrul Chowdhury <sadrul@chromium.org>
Commit-Queue: Lan Wei <lanwei@chromium.org>
Cr-Commit-Position: refs/heads/master@{#590553}
[modify] https://crrev.com/ef148a7c5b01a810bd74d49968aaf00f6ff9f4c4/content/browser/renderer_host/render_widget_host_view_aura.cc

We have submitted the fix, and now it is in canary. Could everyone please try it and tell us if the problem is gone? 

Approved. branch:3538

Seems to be resolved in Canary on Windows 10 1511. Was unable to replicate in Windows 1709 in Stable 69

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/185099b5b486b0cc14049e81073ec4dffb472a88

commit 185099b5b486b0cc14049e81073ec4dffb472a88
Author: Lan Wei <lanwei@chromium.org>
Date: Wed Sep 12 20:59:16 2018

Do not show virtual keyboard for all mouse inputs

We have an issue that Windows virtual Keyboard appears whenever a text
area is selected with the mouse or keyboard. Since we decide to only
show the virtual keyboard when the input type is touch.

TBR=lanwei@chromium.org

(cherry picked from commit ec60a040ccd62e7eb831fa2d359368bd7bf953a8)

Bug:  871756 
Change-Id: Ia804afad907341ed478409d223b67f09c6b7f8f3
Reviewed-on: https://chromium-review.googlesource.com/1194406
Reviewed-by: Pavel Feldman <pfeldman@chromium.org>
Reviewed-by: Marc Treib <treib@chromium.org>
Reviewed-by: Keigo Oka <oka@chromium.org>
Reviewed-by: Lei Zhang <thestig@chromium.org>
Reviewed-by: Navid Zolghadr <nzolghadr@chromium.org>
Reviewed-by: Sadrul Chowdhury <sadrul@chromium.org>
Commit-Queue: Lan Wei <lanwei@chromium.org>
Cr-Original-Commit-Position: refs/heads/master@{#590440}
Reviewed-on: https://chromium-review.googlesource.com/1222677
Reviewed-by: Lan Wei <lanwei@chromium.org>
Cr-Commit-Position: refs/branch-heads/3538@{#341}
Cr-Branched-From: 79f7c91a2b2a2932cd447fa6f865cb6662fa8fa6-refs/heads/master@{#587811}
[modify] https://crrev.com/185099b5b486b0cc14049e81073ec4dffb472a88/chrome/browser/renderer_host/site_per_process_text_input_browsertest.cc
[modify] https://crrev.com/185099b5b486b0cc14049e81073ec4dffb472a88/chrome/browser/ui/search/search_tab_helper.cc
[modify] https://crrev.com/185099b5b486b0cc14049e81073ec4dffb472a88/content/browser/renderer_host/render_widget_host_view_aura.cc
[modify] https://crrev.com/185099b5b486b0cc14049e81073ec4dffb472a88/content/browser/renderer_host/render_widget_host_view_aura.h
[modify] https://crrev.com/185099b5b486b0cc14049e81073ec4dffb472a88/content/browser/renderer_host/render_widget_host_view_aura_unittest.cc
[modify] https://crrev.com/185099b5b486b0cc14049e81073ec4dffb472a88/content/public/test/text_input_test_utils.cc
[modify] https://crrev.com/185099b5b486b0cc14049e81073ec4dffb472a88/content/public/test/text_input_test_utils.h
[modify] https://crrev.com/185099b5b486b0cc14049e81073ec4dffb472a88/ui/views/controls/textfield/textfield.cc

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/d1f14c97f382f26132291814eddf4d6470781d80

commit d1f14c97f382f26132291814eddf4d6470781d80
Author: Lan Wei <lanwei@chromium.org>
Date: Wed Sep 12 21:04:18 2018

Setup the observer before calling DisplayVirtualKeyboard

This is a follow up CL of
https://chromium-review.googlesource.com/c/chromium/src/+/1194406

We should setup the keyboard observer before displaying the virtual
keyboard otherwise the observer won't see the change of the virtual
keyboard.

TBR=lanwei@chromium.org

(cherry picked from commit ef148a7c5b01a810bd74d49968aaf00f6ff9f4c4)

Bug:  871756 
Change-Id: I6b13072ed06d9e10d188c553082b411f2bb09326
Reviewed-on: https://chromium-review.googlesource.com/1220560
Reviewed-by: Sadrul Chowdhury <sadrul@chromium.org>
Commit-Queue: Lan Wei <lanwei@chromium.org>
Cr-Original-Commit-Position: refs/heads/master@{#590553}
Reviewed-on: https://chromium-review.googlesource.com/1222678
Reviewed-by: Lan Wei <lanwei@chromium.org>
Cr-Commit-Position: refs/branch-heads/3538@{#343}
Cr-Branched-From: 79f7c91a2b2a2932cd447fa6f865cb6662fa8fa6-refs/heads/master@{#587811}
[modify] https://crrev.com/d1f14c97f382f26132291814eddf4d6470781d80/content/browser/renderer_host/render_widget_host_view_aura.cc

#58: I downloaded and ran Chrome Canary (71.0.3551.0 (Official Build) canary (64-bit) (cohort: Clang-64)) and found the problem resolved. The keyboard did not appear when the mouse was used to select a text area, but did appear when touch input was used. The issue seems to be fixed in Chrome Canary for Windows 8.1, at least. Thank you! And thanks to all who worked to fix this!

The customers that I have been working with have tried to reproduce this issue in Canary, and have been unable to.  Can we merge this change down to 70?

This bug requires manual review: M70 has already been promoted to the beta branch, so this requires manual review
Please contact the milestone owner if you have questions.
Owners: benmason@(Android), kariahda@(iOS), geohsu@(ChromeOS), abdulsyed@(Desktop)

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

The fix has been merged into M70. Please see Comment 61 and 62.

Confirmed fixed under Windows 10.0.10586 and Canary 71.0.3552.2. 

Thank you!!

When I press CTRL+F, still I get the pop up keyboard.

@69

Can you verify what browser version you are using and OS?  You can find the browser info by typing in chrome://version in the address bar.

@70 the version is 71.0.3562.0 canary (cohort: Clang-32)

I was able to reproduce on Chrome version 71.0.3563.0 on a Windows 10 Yoga. If you try to search by pressing Ctrl + F, the on-screen keyboard pops up, even though a physical keyboard and mouse are attached.

@lanwei, can you take a look?

Of course, I will take a look.

bigo@ could you please check it again, I could not see the virtual keyboard pop up on version 71.0.3568.0, thank you

Was able to repro on 71.0.3569.0 on a Yoga V2.  Laptop was physically in tablet mode, but the windows setting was set to desktop.  The setting "Show the on-screen keyboard when not in tablet mode, and no keyboard attached" was set to on.

Windows 10 version 10.0.16299.611

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/3b034e80b61ecab1cbfa587d6aef1d8263ef3b0b

commit 3b034e80b61ecab1cbfa587d6aef1d8263ef3b0b
Author: lanwei <lanwei@chromium.org>
Date: Thu Oct 04 21:26:59 2018

Do not show virtual keyboard when pressing Ctrl+F

When we use Ctrl+F to open the find bar to seach text in the page, we
should not pop up the virtual keybaord.

Bug:  871756 
Change-Id: I64fa8337668f823aeb6f5d5af2aae0e9fc50e684
Reviewed-on: https://chromium-review.googlesource.com/c/1257582
Reviewed-by: Navid Zolghadr <nzolghadr@chromium.org>
Reviewed-by: Bret Sepulveda <bsep@chromium.org>
Commit-Queue: Lan Wei <lanwei@chromium.org>
Cr-Commit-Position: refs/heads/master@{#596857}
[modify] https://crrev.com/3b034e80b61ecab1cbfa587d6aef1d8263ef3b0b/chrome/browser/ui/views/find_bar_view.cc

Tested and verified in Canary 71.0.3578.0.

https://bugs.chromium.org/p/chromium/issues/detail?id=920553 - New problem is created by this issue. Please check.