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

Issue 804171 link

Starred by 4 users

Issue metadata

Status: Archived
Owner: ----
Closed: Sep 13
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

Touch / HighDPI: Keyboard input directed to address box instead input element of the web page

Reported by andy.bue...@gmail.com, Jan 21 2018

Issue description

UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:57.0) Gecko/20100101 Firefox/57.0

Steps to reproduce the problem:
1. Open browser, go to for ex. www.google.com
2. Click with stylus or finger into the web address box
3. Click with stylus or finger into the search text input field

What is the expected behavior?
Can enter text into the text input field.

What went wrong?
Keystrokes are directed to the address box.

Did this work before? N/A 

Chrome version: 63.0.3239.132   Channel: stable
OS Version: 10.0
Flash Version: Shockwave Flash 26.0 r0

I can re-produce this error on MS Surface Pro 4.
The error does not happen on Lenovo ideapad MIIX 310. Tested only with finger input on this device, does not support stylus.
The Surface tablet has a resolution of 2736x1824 (HighDPI) while the Lenovo ideapad MIIX 310 has 1280x800 pixels.
I guess it's an issue with HighDPI.

It generally occurs on Windows 10 Creators Update and Windows 10 Creators Fall Update.
It occurs when clicked with stylus or finger.
It occurs with on-screen keyboard and also with attached USB keyboard.

It occurs with this chrome versions on Windows 10 Creators Update and Windows 10 Creators Fall update:
63.0.3239.132
62.0.3202.94

It works with this chrome versions on Windows 10 Creators Update and Windows 10 Creators Fall update:
61.0.3163.91
60.0.3112.113
59.0.3071.109
But the stylus works very buggy in this version. Opening dropdowns does not work often, often freezes browser and even the OS occasionally.

It occurs on Windows 10 Creators Fall Update (not in the 1st Windows 10 Creators Update from April 2017):
58.0.3029.81
57.0.2987.133
56.0.2924.76
55.0.2883.87

I tested this mostly with CEF, but i assume this makes no difference.
I tested this also with Chrome browser 63.0.3239.132 and also the latest downloadable build 66.0.3326.0 (530507)

Additional error in Chrome browser: click on the upper right X to close the browser does not work with the stylus.

Btw, at the download page https://commondatastorage.googleapis.com/chromium-browser-snapshots/index.html?prefix=Win_x64/ it would be great if you can show the chromium version number (x.x.x.x), this would make it very much easier to pick a build for testing.
 

Comment 1 by ajha@chromium.org, Jan 23 2018

Components: -UI UI>Input>Touch UI>HighDPI
Labels: Needs-Triage-M63
Cc: vamshi.k...@techmahindra.com
Labels: Needs-Feedback Triaged-ET
Unable to reproduce the issue on reported chrome version 63.0.3239.132 and on the latest canary 66.0.3331.0 using Windows 10 HP EliteBook with the steps mentioned below.
1. Launched Chrome
2. Navigated to www.google.com
3. Clicked on web address box
4. Clicked on search text input field
We are able to see the cursor being at the search input field.Attaching the screen cast of the same.

@Reporter: Could you please check the attached screen cast and let us know if we have missed any steps while reproducing the issue. Any further inputs from your end may help us.

Thanks!
804171.mp4
1.5 MB View Download
In your screen cast it looks as you have used the mouse. Is this the case?
Using a mouse works just fine, the error happens only when i use stylus or finger.

I guess the HP EliteBook has 1920x1080 pixels. Maybe it happens only on higher resolutions.
Please test again with Microsoft Surface Pro tablet.


I will check this error again on another tablet with standard FullHD display (1920x1080)....
Where can i download chrome browser version 66.0.3331.0 ?

Thank you!
Project Member

Comment 4 by sheriffbot@chromium.org, Jan 25 2018

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "vamshi.kommuri@techmahindra.com" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
You wrote "We are able to see the cursor being at the search input field":
On the MS Surface, the cursor is also in the input field when i click on the field with stylus or finger, but when i type a key it gets into the web address box.

Thanks,
Andy
I have tested with version 64.0.3282.0 on 2 other devices:

TREKSTOR SurfTab duo W2
https://www.trekstor-onlineshop.de/SurfTab-duo-W2/en

Lenovo Yoga 2 13
https://pcsupport.lenovo.com/de/en/products/laptops-and-netbooks/yoga-series/yoga-2-13-notebook-lenovo/80dm/59440093/cb35351063/solutions/PD030463

On both the error also occurs - when i use the finger and also when i use the touchpad.
When i click into the text input field the cursor appears in the field and is blinking....
but in fact the address box has the focus, if a text is already entered in the address box it gets selected, and when i start typing the keystrokes are sent into the address box.
This makes the browser not usable on at minimum this 3 devices:
MS Surface Pro 4 (i guess it applies to Pro 3 and later)
Lenovo Yoga 2 13
TREKSTOR SurfTab duo W2

Actually i think this happens on specific types of touchscreens. The MS Surface and the TREKSTOR Tablets both have a Digitizer screen which supports Active Stylus. Don't know if the Lenovo Yoga 2 13 supports Active Stylus, it shows something like "Touch support with 10 touch points" in Windows Settings/About.

If you are working on solving this issue....
Please check also with Windows 8.1, and each major supported Windows 10 version, ie. Anniversary Update, Creators Update and Creators Fall Update.

Thanks,
Andy

Comment 7 Deleted

The error happens also when i connect and use an USB mouse, tested with MS Surface Pro 4 and TREKSTOR SurfTab duo W2 with Windows 10 Creators Fall Update installed.
Thhis bug may not exist on HP EliteBook, maybe it works fine on all HP devices.
But it is really happening on other devices.
I hope you take this issue report for serious and it don't ends like reporting issues to MS.
Status: Archived (was: Unconfirmed)
Archiving old bugs that haven't been actively assigned in over 180 days.

If you feel this issue should still be addressed, feel free to reopen it or to file a new issue. Thanks!

Sign in to add a comment