New issue
Advanced search Search tips

Issue 647536 link

Starred by 3 users

Issue metadata

Status: Fixed
Owner:
Closed: Dec 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug



Sign in to add a comment

Moving the pointer across screen bounds increments pointerId

Project Member Reported by brentons@google.com, Sep 16 2016

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.89 Safari/537.36

Steps to reproduce the problem:
1. Go to http://codepen.io/appsforartists/pen/PGzoam on a computer with multiple screens
2. Move the cursor quickly between screens

What is the expected behavior?
If you are only moving one pointer, you should only see one pointerId.

What went wrong?
Crossing screen bounds seems to increment the pointerId.

Did this work before? N/A 

Chrome version: 55.0.2861.0   Channel: canary
OS Version: OS X 10.11.6
Flash Version: Shockwave Flash 22.0 r0
 
Project Member

Comment 1 by sheriffbot@chromium.org, Sep 16 2016

Labels: Hotlist-Google

Comment 2 by mustaq@chromium.org, Sep 16 2016

Cc: mustaq@chromium.org nzolghadr@chromium.org
Components: Blink>Input
Labels: Hotlist-Input-Dev PointerEvent
Owner: lanwei@chromium.org
Status: Assigned (was: Unconfirmed)
I believe it's an OS-level id bug. If that is the case, perhaps we have nothing to do from Blink.

While thinking about Chrome's bugs from reliance on pre-WM_POINTER API on Windows, it seems possible that Chrome might be using an old low-level API so OS is appearing to behave oddly. Any clue anyone?

Comment 3 by lanwei@chromium.org, Sep 20 2016

I checked it works on Windows, only Mac sometime will show more than one ID. It is not because of the multiple screens, it is because that PointerLeave and PointerEnter events' properties are not set correctly right now on Mac. Their pointer type is empty, ID is not set the same as other pointer events from the same pointer device.
Lan, is this now fixed after your recent changes?
Status: Fixed (was: Assigned)
brentons@ I believe this is fixed as we changed our heuristics on Mac for interpreting what OS passes to us. Let us know if you see it again.

Sign in to add a comment