"pageX" in iframes returns incorrect value on mobile mode.
Reported by
babata...@gmail.com,
Feb 7 2018
|
||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3341.0 Safari/537.36 Steps to reproduce the problem: 1. Open developer tools and enable device toolbar. 2. Choose any device (e.g. "iPad"). 3. Open "index.html". 4. Click any position in the iframe. What is the expected behavior? A correct coordinate in the iframe space is shown. What went wrong? Incorrect "pageX" and "pageY" values, typically negative values, are shown. Did this work before? Yes 63.0.3239.132 stable on Windows Does this work in other browsers? Yes Chrome version: 66.0.3341.0 Channel: canary OS Version: 10.0 Flash Version: This issue can be reproduced on Android Chrome 64.
,
Feb 8 2018
Unable to reproduce the issue on reported chrome version 66.0.3341.0 and on the latest canary 66.0.3342.0 using windows 10 with the below mentioned steps. 1. Launched chrome 2. Opened the attached index.html file 3. Opened DevTools->Device toolbar->Selected ipad 4. Clicked multiple times on the iframe at various positions. We are able to see the correct co-ordinates. Attaching the screen cast of the same. @Reporter: Could you please check the screen cast and let us know if we have missed anything to reproduce the issue. Any further inputs from your end may help us to triage the issue in a better way. Thanks!
,
Feb 8 2018
Thank you for confirmation. In the screencast, there seems to be no "iframe" element in the "Elements" tree. I suspect that the body "test%20index.html" in your desktop is "child.html" I've attached. Please make sure the filename and the contents are valid. 372 bytes: child.html 203 bytes: index.html
,
Feb 8 2018
Thank you for providing more feedback. Adding requester "vamshi.kommuri@techmahindra.com" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Feb 8 2018
I can reproduce this. I'll take a look.
,
Feb 9 2018
Able to reproduce this issue on reported version 66.0.3341.0 and on latest stable 64.0.3282.140 as well using Mac 10.13.3,Windows 10 and Ubuntu 14.04. Placed both HTML files in one folder and opened index.html -- observed negative data in iframe. Good Build: 64.0.3269.0 Bad Build: 64.0.3270.0 You are probably looking for a change made after 516790 (known good), but no later than 516791 (first known bad). CHANGELOG URL: https://chromium.googlesource.com/chromium/src/+log/726d5a2414c2f2986e19f5fab6a1262781a8ac94..35f77bad7ab2a81abbee7cba9ff38872ed76b8dc Reviewed-on: https://chromium-review.googlesource.com/759130 Suspecting same from changelog. Adding RB-Stable for M-64. Please change if not the case. Thanks!
,
Feb 14 2018
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/735fa061d0f531bd0704c4c368d59edc1c1fea3a commit 735fa061d0f531bd0704c4c368d59edc1c1fea3a Author: Navid Zolghadr <nzolghadr@chromium.org> Date: Wed Feb 14 20:59:48 2018 Fix coordinate space for touch pointer events Consider frame scale for calculating coordinates of touch pointer events. Bug: 809942 , 811715 , 809106, 807622 Change-Id: I5503583cd8c0e8b41b7e17fd59170a6f1dff7fa1 Reviewed-on: https://chromium-review.googlesource.com/914690 Reviewed-by: Dave Tapuska <dtapuska@chromium.org> Commit-Queue: Navid Zolghadr <nzolghadr@chromium.org> Cr-Commit-Position: refs/heads/master@{#536813} [modify] https://crrev.com/735fa061d0f531bd0704c4c368d59edc1c1fea3a/third_party/WebKit/Source/core/events/PointerEventFactory.cpp [modify] https://crrev.com/735fa061d0f531bd0704c4c368d59edc1c1fea3a/third_party/WebKit/Source/core/input/PointerEventManagerTest.cpp
,
Feb 26 2018
,
Feb 27 2018
Thank you for fixing! I've confirmed that the issue is resolved on 66.0.3355.2.
,
Feb 27 2018
And thank you for reporting this in the first place. |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by susanjun...@techmahindra.com
, Feb 7 2018