Issue metadata
Sign in to add a comment
|
pointerevent position differs from mousevent positions when registering on a canvas element
Reported by
fun07.ma...@gmail.com,
Feb 9 2018
|
||||||||||||||||||||||
Issue descriptionSteps to reproduce the problem: 1. Visit https://marci4.github.io/testpage/canvaspointerevents.html (or use the attached file) with a device like the Nexus 5X 2. Click on any position on the page (more visible at the bottom right of the page) 3. Compare the two event positions What is the expected behavior? Both event positions are more or less the same. What went wrong? The pointerevent position differs from the mouseevent position. In fact the pointerevent position is in css pixel, the mousevent position is in the pixels respectivly to the canvas element. Did this work before? Yes Chrome 63.0.3239.107 Does this work in other browsers? Yes Chrome version: 64.03282.137 Channel: stable OS Version: Android 8.1.0; Nexus 5X Build/OEM3.171019.014 Flash Version:
,
Feb 12 2018
Tested the issue in Android and able to reproduce the issue. Steps Followed: 1. Launched the Chrome 2. Navigated tohttps://marci4.github.io/testpage/canvaspointerevents.htm 3. Tapped on the page 3. Observed the difference Chrome versions tested: 64.03282.137 OS: Android 8.1.0 Android Devices: Pixel XL 8.1.0 Using the per-revision bisect providing the bisect results, Good build: 64.0.3269.0 Bad build: 64.0.3271.0 You are looking for a change made after 516790(GOOD), but before 516791(BAD). CHANGELOG URL: The script might not always return single CL as suspect as some perf builds might get missing due to failure. https://chromium.googlesource.com/chromium/src/+/35f77bad7ab2a81abbee7cba9ff38872ed76b8dc From the CL's above, assigning the issue to the owner concerned. @nzolghadr: Could you please look into the issue, and assign it to concerned owner if this is not related your change. Please navigate to below link for log's and video-- go/chrome-androidlogs/810706 Note: This issue is not observed in Desktop. Thanks!
,
Feb 12 2018
,
Feb 12 2018
,
Feb 15 2018
Hello everyone, it looks like this is already fixed in the latest Canary: Version: 66.0.3348.0 Can somebody confirm this please? Thank you for the quick fix! Greetings marci4
,
Feb 15 2018
Apparently we have too many instance of this same bug. I'll merge this into another one. I pushed a fix to master yesterday and soon I'm going to merge it to the M65 release branch as well. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by pnangunoori@chromium.org
, Feb 12 2018