High-DPI cursor positions are registering at wrong coordinates in Hangouts, Browser Sample, and Lastpass |
|||||
Issue descriptionChrome Version: 64.0.3257.0 (Official Build) canary (64-bit) OS: ChromeOS High-DPI touchscreen positions and touchpad cursor positions are registering at wrong coordinates in Hangouts on Chromebook Pixel (2015) a.k.a. samus; this broke some time in the last couple weeks on ChromeOS Canary channel Google Chrome 64.0.3257.0 (Official Build) canary (64-bit) Revision 0 Platform 10097.0.0 (Official Build) canary-channel samus Firmware Version Google_Samus.6300.174.0 ARC 4431457 JavaScript V8 6.4.188 What steps will reproduce the problem? (1) Switch Chromebook Pixel (2015) a.k.a. Samus to ChromeOS Canary channel (2) Use built-in high-DPI display (3) Set display to default resolution (Ctrl+Shift+0) (4) Install Hangouts https://chrome.google.com/webstore/detail/google-hangouts/ppleadejekpmccmnpjdimmlfljlkdfej (5) Click icon to open Hangouts window (6) Use touchscreen or trackpad to try to click a Hangouts UI control (7) Resize+reposition window and try again What is the expected result? Clicking should work and control under touch/cursor should be active both times What happens instead? Control at coordinates halfway between touchpoint and Hangouts window origin (upper-left corner) is activated in each case Please use labels and text to provide additional information. For graphics-related bugs, please copy/paste the contents of the about:gpu page at the end of this report.
,
Nov 7 2017
Also to add to that this is on a Macbook Pro running Ubuntu and I'm just using a mouse. Not touchpad
,
Nov 7 2017
What is your devicePixelRatio? Mine is 2 according to data:text/html,<script>document.write(devicePixelRatio)</script>
,
Nov 7 2017
my devicePixelRatio is 2
,
Nov 7 2017
Browser Sample is affected too, but coordinate warping happens only inside its web content area -- coordinates for the top UI control bar are fine: https://chrome.google.com/webstore/detail/browser-sample/edggnmnajhcbhlnpjnogkjpghaikidaa
,
Nov 7 2017
,
Nov 7 2017
,
Nov 7 2017
,
Nov 7 2017
This may be the best kind of bug - the kind that's already fixed at HEAD :) This Chromebook just updated to 64.0.3261.0 (Official Build) canary (64-bit) and it's fixed ☺
,
Nov 7 2017
[chrome mac triage] Closing this since it's fixed |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by jferl...@gmail.com
, Nov 7 2017