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

Issue 905768 link

Starred by 2 users
Status: Archived
Owner: ----
Closed: Nov 29
Cc:
█ krajshree@chromium.org
eirage@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug-Regression



Sign in to add a comment

navigator.maxTouchPoints returning 256 on device with no touch

Reported by msch...@bclc.com, Nov 15 
UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.53 Safari/537.36

Steps to reproduce the problem:
1. Open a page, enter in console navigator.maxTouchPoints
2. Sometimes you get 256 returned

It isn't consistent, but I have created a webpage with nothing but the doctype, and console.log(navigator.maxTouchPoints) and got 256.

What is the expected behavior?
returns 0

What went wrong?
Chrome returns 256 touch points when the correct value is 0

Did this work before? Yes 

Chrome version: 71.0.3578.53  Channel: beta
OS Version: 10.0
Flash Version:

Comment 1 by swarnasree.mukkala@chromium.org, Nov 16

Labels: Needs-Bisect Needs-Triage-M71

Comment 2 by krajshree@chromium.org, Nov 16

Cc: krajshree@chromium.org
Labels: Triaged-ET Needs-Feedback
Unable to reproduce the issue on win-10 using chrome reported version #71.0.3578.53 and latest canary #72.0.3611.0.
Attached a screen shot for reference.

Following are the steps followed to reproduce the issue.
------------
1. Opened a page, entered in console navigator.maxTouchPoints.
2. Observed that 0 was returned as expected.

mschwab@ - Could you please check the issue on latest canary #72.0.3611.0 by creating a new profile without any apps and extensions and please let us know if the issue still persist or not.

Thanks...!!
905768.PNG
81.3 KB View Download

Comment 3 by dtapu...@chromium.org, Nov 19

Components: -Blink Blink>Input

Comment 4 by nzolghadr@chromium.org, Nov 22 

Reporter could you provide more information on your system. It seems that it is not reproducible on our side. A trace and maybe a recoding would really be helpful as well.

Comment 5 by nzolghadr@chromium.org, Nov 22

Cc: eirage@chromium.org

Comment 6 by nzolghadr@chromium.org, Nov 29

Status: Archived (was: Unconfirmed)
There wasn't any feedback from the reporter since the last time. Closing this for now. 
Reporter, if you happen to see the issue again feel free to comment here or file a new issue and provide the additional information requested. Thanks.
►

Sign in to add a comment