Enter a large topic (> 100 posts is good, but sometimes it happens on smaller topics). Read the topic and use j to move from post to post. Eventually the scrolling just stops. Right before that happens, the red bar to the side of the active post (for the purposes of j) disappears. This GIF shows it, with fast frame rates while it is working, and slow frame rates when it fails:
When this happens, I can get it working again by scrolling down with my mouse wheel. I suspect that what I’m seeing is the mouse wheel scroll knows how to trigger the “load next batch of posts” javascript, while the j scroll does not.
Nah, I found it super simple to reproduce in that particular 300+ post topic. Just start reading from the top. First stop for me was at 38, second at 58, and several more going down. I’m using Firefox (still 46 here) on Linux.
Looks to be because it is failing to load more topics unless you move the scrollwheel on your mouse (or move the scrollbar up and down to trick it into loading more topics).
It’s not always happening because of the length of posts. I don’t know when Discourse is fetching the next batch of posts but when a long post is the last loaded one, then it may be too far down to trigger the load since the commit moved the current visible/selected post down a lot.
I believe this is the bug that @zogstrip has seen. We are still working on getting a good repro. I’ve unfortunately never been able to reproduce it locally.
