Issue metadata
Sign in to add a comment
|
HitTestResult incorrect, different from hilighted link
Reported by
anthonyo...@gmail.com,
Dec 24 2017
|
||||||||||||||||||||||
Issue descriptionSteps to reproduce the problem: 1. Load a web page with links close to each other, like https://news.ycombinator.com/ and check for HitTestResult on link long press. 2. Long press on a link so you see the link highlight. 3. Often, HitTestResult will return a result from an adjacent link instead of the expected, highlighted link. What is the expected behavior? HitTestResult should always result in URL of the intended, highlighted link. What went wrong? It seems that whatever is determining the HitTestResult is running later than expected when perhaps the finger has moved a bit, or that a different algorithm is used to determine HitTestResult as compared to whatever causes the link to highlight. In the attached screenshot, the HitTestResult is show in the context menu as a URL from wsj.com. However, in the background you can see that the underlined "14 comments" link is the one that was long-pressed. The HitTestResult should be for "14 comments" at news.ycombinator.com. If you move your finger an infinitesimal amount after long pressing, you can more easily reproduce this although it is not necessary. You will see the behavior. Did this work before? Yes Android 7 Chrome version: 63.0.3239.111 Channel: n/a OS Version: 8.1.0 Flash Version: n/a Interestingly, the same version of Chrome on Android 7 does not exhibit this result. System WebView also exhibits this behavior on Android 8.1 but not on Android 7. HitTestResult has always been more accurate in older Android versions that I have seen: Eclair, Froyo and all others all the way to Nougat. The one exception was on a Nexus 7 (2013) running Android 5.1.1. It exhibited this same behavior but I always it was due to a hardware issue with the screen which had been publicized. Could there be a similar issue with the Pixel 2 screen?
,
Dec 26 2017
,
Dec 26 2017
Tested the issue in Android and could not reproduce the issue. Observed the corresponding URL is seen on context menu . Steps Followed: 1. Launched Browser 2. Navigated to https://news.ycombinator.com 3. Long tapped on URL and observed the corresponding URL is seen on context menu Chrome versions tested: 63.0.3239.111 OS Android 8.1.0 Android Devices Pixel XL 8.1.0 @anthonyorciuoli: Could you please let us know the details of your device and if possible attach a screencast fro your end as well for further triaging of the issue. Thanks!!
,
Dec 28 2017
> details of your device > screencast I can work on a screencast, but anyone using a Pixel 2 / current stock OS 8.1.0 / current Chrome (or WebView) as specified above? able to try this?
,
Dec 28 2017
Thank you for providing more feedback. Adding requester "sandeepkumars@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jan 2 2018
Please see attached video. First few seconds shows the links: - top "40 comments" link goes to ycombinator.com comments page - bottom "Tiananmen Square 1989 death..." link goes to bbc.com article @ 6 seconds: The first time "40 comments" is long-pressed you can see the HitTestResult is correct, ycombinator.com. @ 10 seconds: "40 comments" is long-pressed again and you can see the HitTestResult is incorrect, bbc.com. To reproduce this, long press a link where the link below it goes farther across the web page than the top link, like this: top link to long press longer bottom link that will sometimes give HitTestResult You may also have to try several times to reproduce the issue. The video was taken using Lightning Browser, but same happens in Naked Browser / other WebView apps.
,
Jan 5 2018
Tested the issue using #63.0.3239.111 on Pixel 2; 8.1.0 and could not reproduce the issue. Requesting someone from UI>Browser>Core team to take a look at this issue. Thanks!!
,
Apr 5 2018
@Reporter: Are you still able to reproduce the issue using latest Chrome #65.0.3325.109? Thanks!!
,
May 23 2018
As there is no action on this issue for long time closing this issue. Request you to update your Chrome to latest #66.0.3359.158 and verify. Feel free to file a new issue if the issue is still reproduced at your end. Thanks! |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by anthonyo...@gmail.com
, Dec 24 2017