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

Issue 719320 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Jul 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

[Forum M57] - Touchscreen on Chrome Results in Right-Clicking

Project Member Reported by jainabhi...@chromium.org, May 8 2017

Issue description

Chrome Version: M57+
OS: Windows (Touchscreen devices)

What steps will reproduce the problem?
(1) Visit a URL
(2) Click on touchscreen

What is the expected result?
Clicking on touchscreen should work as left click (Similar to a trackpad)

What happens instead?
Touch screen click behaves as if user right clicked
Video : https://www.youtube.com/watch?v=4n4ub9O5SAI

GPU Errors for one of the user (NVIDIA GeForce GT 750M)
[12584:10428:0411/134944.297:ERROR:gles2_cmd_decoder.cc(17287)] : [.DisplayCompositor-0000025438F2D4F0]GL ERROR :GL_INVALID_OPERATION : glCreateAndConsumeTextureCHROMIUM: invalid mailbox name
[12584:10428:0411/134944.297:ERROR:gles2_cmd_decoder.cc(9579)] : [.DisplayCompositor-0000025438F2D4F0]RENDER WARNING: texture bound to texture unit 0 is not renderable. It maybe non-power-of-2 and have incompatible texture filtering.
[12584:10428:0411/134944.297:ERROR:gles2_cmd_decoder.cc(17287)] : [.DisplayCompositor-0000025438F2D4F0]GL ERROR :GL_INVALID_OPERATION : glCreateAndConsumeTextureCHROMIUM: invalid mailbox name
[12584:10428:0411/134944.297:ERROR:gles2_cmd_decoder.cc(9579)] : [.DisplayCompositor-0000025438F2D4F0]RENDER WARNING: texture bound to texture unit 0 is not renderable. It maybe non-power-of-2 and have incompatible texture filtering.
GpuProcessHostUIShim: The GPU process exited normally. Everything is okay.

Other GPU details are in Forum post.
Forum : https://productforums.google.com/forum/#!msg/chrome/Hf0DiJpszXU/-Rk2ly5rAwAJ
 
Cc: gov...@chromium.org
Another confirmed user report with video
https://youtu.be/Ni0-P7kYcGc

Comment 2 by gov...@chromium.org, May 11 2017

Cc: pbomm...@chromium.org
pbommana@, could you please try to repro and bisect if possible. Thank you.
We aren't able to reproduce the issue, If possible can we get below details from user's  :

1. Is this specific to Surface book laptops 
2. Is the issue specific to Chrome or across the machine. 
3. Are they still seeing this behavior on 58.0.3029.110(latest Stable)

thank you in advance.




Comment 4 by fishe...@gmail.com, May 11 2017

Hello,

I was asked by the community specialist to add my input to this report. I am one of the people having this issue.

- So far I have had the problem on both a Surface Pro 3 Tablet and  Surface Book laptop. The Pro was bought at least 2 years ago, the Book was bought a week ago. I have not tried it on any other computers that have touchscreens.

-The problem is only in Chrome; as soon as I leave Chrome, the touchscreen works perfectly inside Office, Edge, and the Desktop.

- I have been dealing with this issue at least a year now on the Pro, and I have kept my Chrome updated to the latest at all times. I have tried incognito mode as well as Canary and the problem does not go away. I have clean installed Windows, reinstalled Chrome a number of times, removed all extensions, removed any skins, and tried it without my profile added to the Chrome.

- I have seen a suggestion that this could be related to damaged files inside of my Chrome profile. I tried to deleting my local files and redownloading my profile to the computer, but it did not work. I have far too much data and information to risk deleting all files to fix the problem, so that would take a serious last resort to get me to do.
Cc: robliao@chromium.org ananta@chromium.org
Labels: Proj-TabletChrome

Comment 6 by girard@chromium.org, May 12 2017

Thanks for the bug report/video, and thanks for your help in diagnosing it.

From the video, it looks like chrome is treating a tap as a two-finger tap. Perhaps we've gotten confused and lost track of a touch? We could get some diagnostics from https://rbyers.github.io/eventTest.html - I expect when you tap the screen the touch event will show up as "touch 1..." instead of "touch 0..."

You commented that this has been happening for a year - was touch functioning on your device previously?

Comment 7 by fishe...@gmail.com, May 12 2017

So I should go to that website on the tablet/laptop and then start trying
to use the touch screen? We have traveled a bit past my skill set in
computers, so I might need walked through this process a bit.

that is exactly what is happening, it thinks I am two finger touching
whenever I touch with a single finger.

So within a few hours of setting up my Surface Book, the problem started.
With my Surface Pro 3, I only remember it happening starting about a year
ago or so, but I honestly do not remember for sure. I don't THINK it was
happening for the year six months or so that I had it.

Regards,

Justin Fisher
206-653-5351
Fisheraf@gmail.com

Comment 8 by fishe...@gmail.com, May 15 2017

I have been playing around with this diagnostic tool you provided me but I
am not sure how I am supposed to share the data with you, or if I am
supposed to config it a certain way. I played around with the browser with
the program live and once the issue began and I saw it happening on the
screen ( i would tap the screen on the diagnostic page and the double click
action would happen) often times as well a single tap would cause the page
to scroll indefinitely until i tapped it again to stop it.

Please advise what exactly you are looking for from me in this program.

Regards,

Justin Fisher
206-653-5351
Fisheraf@gmail.com

Comment 9 by fishe...@gmail.com, May 27 2017

I am not entirely sure how, but it appears to have been fixed on my Surface
Book Laptop. I have not had the problem in several days. Was there an
update released?

Regards,

Justin Fisher
206-653-5351
Fisheraf@gmail.com
Status: WontFix (was: Untriaged)
Hi there Justin - It sounds like your issue has been corrected with one of our updates. I'm going to close this for now, but please reopen if this happens again.

Comment 11 by fishe...@gmail.com, Jul 25 2017

It actually has vanished completely on both devices. Thank you so much for
figuring this out for me!

Regards,
Justin Fisher

Sign in to add a comment