This has also been observed on https://nextcloud.com/blog/mobile-note-taking-with-your-private-cloud-announcing-joplinnextcloud-integration/. It happened much more quickly on here.

Happens here as well. https://www.w3schools.com/angular/ng_ng-app.asp

I'm beginning to think this isn't site specific, but might be related to something external, like my DE, GNOME.

Unable to reproduce the issue on ubuntu 17.10 GNOME 3.26.1 using chrome reported version #65.0.3325.162 and latest chrome version #67.0.3377.0.

Attached a screen cast for reference.

Following are the steps followed to reproduce the issue.
------------
1. Browsed to https://twitter.com while logged in
2. Scrolled down for a bit
3. Observed that scrolling worked smoothly without any issues.

reporter@ - Could you please check the issue on latest chrome version #67.0.3377.0 by creating a new profile without any apps and extensions and please let us know if the issue still persist or not.

Thanks...!!

Deleted: 823765.webm 14.5 MB

	823765.webm 14.5 MB View Download

Likely a dup of one of your other bugs.

I've just installed version 67.0.3371.0, created a new profile with no extensions, logged into Twitter, and scrolled. After a few loads after reaching the "bottom" of the endlessly scrolling page, scrolling eventually stopped working.

It would appear this may have been an Nvidia driver issue, upgrading to 390.48 seems to have resolved the issue.

Disregard my last comment, the issues persists, though I do think it may be driver related.

Also observed on 65.0.3325.181 in Windows 10.

This seems like a dup of https://crbug.com/797708 and some other bugs.

Sounds like it, this can be closed as a dup then.

Looks like if you keep scrolling while the page is loading because of an infinite scrolling, the scrolling doesn't work and you have to wait for page load to finish and then resume scrolling.

Removing the duplication for now to make sure that the issue is a duplicate of 828235.

dmuc2005@ could you please be more specific about when you see the bug?

Does it only happen when you are at the extent of the page and the page is trying to load some new content? or does it happen in random positions of the page without being at the extent? I could only reproduce the issue on twitter only on the first case.

Also could please confirm if the issue still exists on M66 or not? A few scroll related bugs have been fixed on 66 and this might be a duplicate.

If the issue still happens on 66, could you please record a trace by using chrome://tracing/ ? please make sure that the input latency category is selected. 

FYI: Here are the instruction for recording a trace: https://www.chromium.org/developers/how-tos/submitting-a-performance-bug