Some more information:
This is happening on 300+ devices across many sites.

They are HP MX12 touch screen, 12" tablets with a docking station.
Having a USB keyboard or mouse connected doesn't seem to make any difference to the behaviour.
I'm loading Win10 1809 on a device for further testing now.

The tablets are NOT in tablet mode.

Chrome is running in a maximised window.
Previously they were running in app mode or kiosk mode, but because the address bar was hidden completely there was no work-around to show the keyboard.

Thanks,
Callan

Hi Susan, please let me know if you need any video or other details from my client machines to help here.
thanks,

Callan@ Thanks for the issue.

Tested this issue on Windows 10 1803 Surface Pro 4 on the reported version 70.0.3538.102 and unable to reproduce the issue by following the below steps.

1. Launched Chrome and made sure the tablet mode is not enabled.
2. Navigated to http://id.bp.com/ and touched the input field and can observe that the onscreen keyboard appears as expected.
Attached is the screen cast for reference.

Request you to check and confirm if anything is missed from our end in triaging the issue.
Also request you to retry the issue on a new chrome profile without any flags/extensions and update the thread with the observations.

Thanks..

Deleted: 906957.mp4 2.1 MB

	906957.mp4 2.1 MB View Download

Hi Susan thanks for this.
Can you try opening the chrome window directly to the URL id.bp.com, instead of navigating to the page using the address bar?

Clicking on the address bar somehow activates the on screen keyboard for use on input fields directly after.

You can use this powershell code to launch the window:

$chrome="c:\\Program Files (x86)\\Google\\Chrome\\Application\\Chrome.exe"
$FT = "https://id.bp.com"
&$chrome  $FT -no-default-browser-check --disable-pinch --no-first-run -overscroll-history-navigation=0 --DISABLE-BACKGROUND-NETWORKING --disable-features=AutoplayIgnoreWebAudio --start-maximized  --new-window 

Thanks & Regards,
Callan

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

Heres the bug in action on my surface pro:
https://youtu.be/2gQ1gnLAjvM

See also bug 497381(Touch Keyboard not invoked), fixed in M67 with Redstone RS4+, aka windows build 1803, 1809; however still getting recent regression failures:

==
Bug 497381  11 /5 #140:
This bug exists in the following X64 version,
1. Current stable: 70.0.3538.77
2. Current beta: 71.0.3578.30
3. Current Dev: 72.0.3595.2
4. Current Canary: 72.0.3602.0

The only working version is previous beta: 71.0.3578.20
Operating Environments: Thinkpad X1 Tablet, Windows 10 Pro 1809 X64

==
Bug 497381  11 /21 #143 broken in 70.0.3538.110(stable), 71.0.3578.62(beta)
with trivial test page example.

Pls CC dtapuska@chromium.org

Bug 497381 fix was reverted in M69 due to COM issues and 497381 has been re-opened as assigned.

This CR looks like a merge dup of 497381?

@Larry I think they might be related.
497381 talks about having Win10 in Tablet mode, where 906957 has Chrome in desktop mode.
It may be the same fix - I'll take your guidance if 906957 should be closed as a duplicate.

I think that 497381 was marked as fixed or closed the first time I visited that bug, but I'm glad to see it now showing as open (assigned)

Callan@ Thanks for the update.

As per comment #10, merging this issue to issue 497381,removing 'Needs-Bisect' label and CC'ing dtapuska@ for further updates on this issue.
Please feel free to undupe if this is not similar.

Thanks..