screenX of touch event is relative to the window rather than screen.
Reported by
babata...@gmail.com,
Feb 19 2018
|
|||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3350.0 Safari/537.36 Steps to reproduce the problem: 1. Open https://jsfiddle.net/0bxexwxa/3/ on touch-ready Windows PC. 2. Touch anywhere. (Please do not maximize the Chrome window so that window.screenX has non-zero value). What is the expected behavior? The coordinate values displayed under "pointerdown" and "touchstart" are in screen-space (relative to the physical screen topleft). What went wrong? The displayed coordinates are window-relative. Since the "screenX" value for a mouse event is correctly relative to the screen, the displayed values under "pointerdown" are different in the case of clicked by mouse and touch. Did this work before? N/A Does this work in other browsers? Yes Chrome version: 66.0.3350.0 Channel: canary OS Version: 10.0 Flash Version:
,
Feb 20 2018
Unable to reproduce this issue on reported version 66.0.3350.0 using Windows 10 touch laptop. Attaching screencast for reference. 1. Opened attached JSFiddle and touched near 2.5 and observed results. 2. Now opened same JSFiddle in Chrome M60 and Firefox. Observed same results. @Reporter: Could you please check the video and let us know if we miss anything from steps. Also could you please elaborate "touch event is relative to the window rather than screen" and please guide us in triaging the issue further.
,
Feb 20 2018
Thank you for confirmation, and sorry for my lack of explanation. The issue is prominent when the Chrome window is placed to right of the Desktop. Please see the attached video. - Firstly, I've clicked by mouse around "pointerdown" at 00:00:07, then the result was "x=1971, y=895" (correct). - Next, I've touched by my finger near it at 00:00:10, then the result was "x=900, y=855.33..." (incorrect: x is too small).
,
Feb 20 2018
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Feb 21 2018
Able to reproduce this issue on Win-10 and Ubuntu 14.04 touch screen using chrome reported version #66.0.3350.0. Unable to check the issue on mac as we doesn't have a mac touch screen. This is a non-regression issue as it is observed from M60 old builds. Hence, marking it as untriaged to get more inputs from dev team. Thanks...!!
,
Sep 13
Archiving old bugs that haven't been actively assigned in over 180 days. If you feel this issue should still be addressed, feel free to reopen it or to file a new issue. Thanks! |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by krajshree@chromium.org
, Feb 19 2018