New issue
Advanced search Search tips

Issue 676135 link

Starred by 3 users

Issue metadata

Status: Duplicate
Merged: issue 675567
Owner: ----
Closed: Jan 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 2
Type: ----



Sign in to add a comment

Screen jumps to selected links

Reported by twd...@gmail.com, Dec 20 2016

Issue description

Device name: LG G2 - d800

From "Settings > About Chrome"
Application version: 56.0.2934.23
Operating system: Android 6.0.1 (Cyanogenmod 13)

URLs (if applicable):

Steps to reproduce:
(1) Long press a link on a web page
(2) Close long press menu
(3) Scroll away from link (without clicking anywhere on the page, such that the link is still "selected") 

Expected result: Able to scroll up and down page as normal. 


Actual result: Page jumps back to selected link until link is unselected by clicking on an empty part of page. 




 
i think i have noticed that as well but not sure if its the same bug.  i recorded it:

https://youtu.be/7Pe-hyM3qVY
it doesn't happen in the non beta version of Chrome 

Comment 3 by twd...@gmail.com, Dec 22 2016

Yep that's the same bug! I'm fairly certain t showed up in the v55 -> v56 beta update ~2 weeks ago. It must not have reached the stable channel yet. I found two other reports of it here and here:

 Issue 674094 : https://bugs.chromium.org/p/chromium/issues/detail?id=674094

 Issue 675343 : https://bugs.chromium.org/p/chromium/issues/detail?id=675343
Cc: acindhe@chromium.org
Components: Blink>Scroll
Labels: triage-te
Cc: bokan@chromium.org
Labels: -Pri-3 Pri-2
Do you have Android Accessibility on?  Issue 675343  is only occurring if accessibility is on.

Also that issue has been fixed in latest beta. Can you check Chrome Beta and see if it still happens: https://play.google.com/store/apps/details?id=com.chrome.beta&hl=en

/cc bokan@: can this be related to  issue 675343 






Comment 6 by bokan@chromium.org, Jan 5 2017

Mergedinto: 675567
Status: Duplicate (was: Unconfirmed)
Yup, and that was a dup too. This should be fixed in the latest Beta push.

Sign in to add a comment