Video of behaviour
https://www.youtube.com/watch?v=IYJVdGJFhXA

Another discussion here of it happening to Google's own search results in the Google app and Chrome. 

https://plus.google.com/+ArtemRussakovskii/posts/AumEMQj4hMF

We are unable to reproduce the issue on build 56.0.2924.23. we are able to scroll down to the bottom of the page without any issues.could u please give us more information about the device model and bug report if possible.

#5, have you read the comments on the gplus link, very wide spread including webview used by the Google Search app? 
Click the link, opens a new tab, press back to close the tab, don't tap on the screen but drag/flick scroll. You'll notice the link remains in focus with a (new to M56) orange border.

Current build 56.0.2924.23 on a Pixel XL 7.1.1 (ps why in About Chrome can't I long press to copy the build and device data, a lot easier than having to open and close it sevwral times to write this comment). 

Having tried to work out what others may have reported a similar issue with other keywords I've found a collection of identical bugs for "android scrolling". 
 Issue 674094  appears to have moved the furthest pin pointing the issue to Accessibility, turing it off Wakey (the only app with permission) has resolved the issue for me. 
Feel free to merge issues.

In my case, it was switching WebView implementation from Canary to any other one, like stable in Android system dev settings.

The odd part was that it was set to Chrome Beta originally, yet when I set it to Beta again, it worked fine. Only setting to Canary exhibited the issue. This may be a bug in the selector in core Android itself (Canary was installed most recently of all Chrome flavors). 

 Issue 674026  has been merged into this issue.

Exactly bisected to https://codereview.chromium.org/2465403003 "Android accessibility: automatically focus links" using the following repro steps:

1. Open http://mobile.nytimes.com/comments/2017/01/02/opinion/donald-trump-bureaucracy-apprentice.html on a Galaxy S7 (which presumably has some accessibility service enabled)
2. Tap "Reader Picks"
3. Try to scroll down.  Observe scroll keeps bouncing back to top of page.

As dmazzoni@ is on vacation this week, I'll revert.

Reverted as http://crrev.com/441248 .  Requesting merge of revert.

 Issue 675343  has been merged into this issue.

Your change meets the bar and is auto-approved for M56. Please go ahead and merge the CL manually. Please contact milestone owner if you have questions.
Owners: amineer@(clank), cmasso@(bling), gkihumba@(cros), bustamante@(desktop)

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/02219589656825cba76ea57e307c1345b52bfea5

commit 02219589656825cba76ea57e307c1345b52bfea5
Author: Alexandre Elias <aelias@chromium.org>
Date: Thu Jan 05 00:22:39 2017

Revert of Android accessibility: automatically focus links (patchset #3 id:40001 of https://codereview.chromium.org/2465403003/ )

Reason for revert:
Caused scrolling bug  http://crbug.com/675567 

BUG=657157, 675567 

Original issue's description:
> Android accessibility: automatically focus links
>
> When setting accessibility focus to a node, auto-focus it if it's a link.
> This is needed for some sites that have skip links that are only visible
> when focused. It might be possible to auto-focus more than just links but
> this seems the safest.
>
> Fixing this exposed a race condition with our code to refocus the node with
> accessibility focus if its location has changed - essentially when you
> click on the skip link, the skip link was changing its location, causing us
> to fire notifications on it because its location had changed - but that
> was racing with the real change to accessibility focus from following the
> skip link.
>
> Fix this race condition by re-focusing the node with accessibility focus
> after a short delay, and canceling the delayed task if accessibility
> focus changes again.
>
> Tested manually with two urls that exercise these code paths.
>
> BUG=657157
> TESTED=http://getbootstrap.com/ and http://jsfiddle.net/mev0c4dt/show/
>
> Committed: https://crrev.com/fd9566093da77d9413ba61f8be1b6e03daaadf33
> Cr-Commit-Position: refs/heads/master@{#430006}

TBR=dtseng@chromium.org,sgurun@chromium.org,dmazzoni@chromium.org
BUG=657157

Review-Url: https://codereview.chromium.org/2609313002
Cr-Commit-Position: refs/heads/master@{#441248}
(cherry picked from commit 12c8f43c72337a88c60abaa36a9b0e8adbba9453)

Review-Url: https://codereview.chromium.org/2615443006 .
Cr-Commit-Position: refs/branch-heads/2924@{#674}
Cr-Branched-From: 3a87aecc31cd1ffe751dd72c04e5a96a1fc8108a-refs/heads/master@{#433059}

[modify] https://crrev.com/02219589656825cba76ea57e307c1345b52bfea5/content/browser/accessibility/browser_accessibility_manager_android.cc
[modify] https://crrev.com/02219589656825cba76ea57e307c1345b52bfea5/content/public/android/java/src/org/chromium/content/browser/accessibility/BrowserAccessibilityManager.java

Its working fine on latest M56 build. Thanks 

Verified fix with Chrome Beta release '56.0.2924.53'

 Issue 677375  has been merged into this issue.

 Issue 676135  has been merged into this issue.

I’m not sure if you’re saying this is resolved, but it isn’t.  Chrome Beta still has this issue, although it has gotten better.  

 

Click a link and then click back to the original page and stuck you are again before refreshing.

 

~NaughtyHotty

 

From: bo… via monorail [mailto:monorail+v2.3285626211@chromium.org] 
Sent: Thursday, January 05, 2017 10:45 AM
To: evelswoman@gmail.com
Subject:  Issue 675567  in chromium: Page snaps back to focused links

Issue 676468 has been merged into this issue.

I have just installed the latest beta, and from what I've seen this far, all problems are gone. 
Thanks guys! 

Re#23: What's changed that it's gotten better? Could you post the version number you're on? If it's still reproducing, try going to Android Settings > Accessibility and turn off all the services, see if that helps.

I can also confirm that the bug is fixed in latest beta installed today. 

 Issue 674094  has been merged into this issue.

Dev channel still seems to not have the revert which may explain why I can still see the bug in dev 57.0.2970.0 while beta (56.0.2924.53) works fine.
This might explain #23.

 Issue 677551  has been merged into this issue.