A discussion is ongoing about issues with infinite scrolling on the index page/topic list. ljpp initially reported receiving several comments about the issue, but no repro pattern has been found. The problem has been intermittent since 2017 and has recently resurfaced.
ljpp suspects the issue may be specific to Android/Chrome clients, but a repro pattern is difficult to establish due to the rarity and randomness of the issue. codinghorror suggests trying to narrow down the problem by checking browser version, plugins, and testing in safe mode or a different browser.
Falco recommends using Discourse Safe Mode to isolate the issue. ljpp notes that the issue may not be widespread, and a workaround suggested by a user involves turning the phone to landscape mode, but this is unconfirmed. The issue remains ongoing, with ljpp continuing to investigate and seeking updates.
One thing to narrow down is browser version and plugins. Is it specific to a particular set of users? Have they tried in browser safe mode, or in a different web browser?
Since you have a custom index theme that overwrites templates it’s a good idea to try to reproduce with How to use Discourse Safe Mode to narrow it down.
As this topic is not flooding with comments, it seems that this is not a common issue. We’ll try to narrow it down, if possible. This is always a bit of a challenge, as we are not a tech community.
My educated guess is that for some reason Android/Chrome is more prone to these rather random issues, than for example iPhone/Safari. I have a clean Android One device and very rarely have any issues.
Please keep the topic open. I’ll post an update if I find anything useful, or request a close if this disappears on it’s own – like it has before.
This is still randomly happening. The issue is rather rare and really random, so repro pattern is not available, unfortunately.
One user of ours suggested that turning the phone to landscape would be a workaround, but I have not seen this lately so cannot confirm if there is any truth to this.
Also, I relate this issue specifically to Anrdoid/Chrome clients.