In a long topic, choose one with over >200 replies (there are quite a few here on Meta), then scroll as far down as possible until you see it loading more replies.
Sometimes, when the screen gets a bit ‘stuck’ (I’m not sure how to explain this), and the replies, instead of the next batch appearing below the last post, continues going on, in each batch, and you can still see the loading circle, loading more on more replies, but you are always at the bottom of each batch each time, until you reach the last post of the topic.
I experience this on mobile here on Meta, but is this the expected behaviour?
AI-generated summary
A discussion is taking place about an issue with scrolling to the bottom of a long topic on a Discourse forum. NateDhaliwal (#1, #2, #6) describes the problem, where scrolling to the bottom of a topic with over 200 replies causes the next batch of replies to load without stopping, making it difficult to read the content. HamMan2118 (#3) suggests that this might be normal behavior to reduce loading times. However, sam (#4, #7) mentions that a rewrite of the topic page is planned, which may fix the issue.
david (#8) points out that a fix has been implemented, which resolves the issue by anchoring the browser onto post-stream content instead of the timeline. Overgrow (#9, #10) confirms that the glitch has been corrected, but notes a minor aesthetic issue with the URL changing to the last post on Android devices.
2 Likes
To give an example:
You are looking at batch X of replies (say, 20 in 1 batch). You scroll to the bottom, where it loads the next batch (batch Y). Instead of allowing you to keep scrolling to read the replies in batch Y, it jumps to the bottom of batch Y where you can see it’s loading batch Z. And this continues. You can scroll up to read what happens in that batch you are in (and previous batches), but it will jump to the next batch anyway.
I think I see what you mean - tested it myself and I can reproduce the problem.
I’d think is is normal behavior to reduce loading times on topics, as 90% of the time a user won’t be rapidly scrolling through a topic unless they want to go to a specific post. In that case, they can type the post number they want to go to in the URL bar.
1 Like
We have a rewrite of the topic page this year queued and I think we will fix it then. putting pr-welcome now in case someone wants to fix it earlier.
4 Likes
3 posts were split to a new topic: New topic map causing infinite-loading loop
@sam Is the rewrite finished? I think this bug still occurs on Meta.
Also, on Glitchy Scrolling.
Rewrite is not done, some time this year
4 Likes
This issue should be resolved by
Prior to that fix, the timeline would often be chosen as the scroll-anchoring point when scrolling down. So when the new posts rendered above, the browser would lock onto the timeline instead of the new post content.
,
With the fix, the browser now anchors onto post-stream content:
7 Likes
It has improved a lot, thank you!
4 Likes
The glitch is corrected, but it seems that the URL changes to the last post though (at least on Android). When you start scrolling again it gets the correct post number and counts correctly from there. It’s just aesthetic, but I thought I let you know.
1 Like
This topic was automatically closed after 6 days. New replies are no longer allowed.