Ever since updating to the latest version of Discourse, we’ve been getting fairly widespread complains about issues while scrolling through discussions that have lots of Twitter / X embeds.
Here are some example pieces of user feedback:
I noticed with anyone posting especially multiple x/tweet embeds in a post let alone whole thread full of them, it glitches sometimes multiple times, it reloads those embeds and that messes up cursor location in page where I was reading and I have to browse back. It can happen in other threads too but these x embeds certainly break it often.
…
But I am seeing the pages move up and down. I’ll be reading a post and then the page will jump up or down a few pages. Then I have to scroll to get back to where I was reading. Then it happens again. I’ll have to scroll back to where I was reading again. It happens a lot.
…
On my Samsung Phone on Brave, on My microsoft Laptop on Brave, IE Edge and Chrome. On my above phone linux laptop on Brave. I see it on every device that I have. Lots of people are noticing in that thread as well, plus I got a call today from my brother Joe who is an Insider about it.
Anecdotally, I think it happens on fast internet connections. I have 2 GB bi directional fiber.
…
For me, it is when I allow the embedded Twitter/X posts to be shown. Stuff like that is blocked by default on Firefox, so I click to allow them.
Then, every time there is a new post on the thread, it jumps and the X posts reload and I have to scroll back to where I was. Did it loads today while reading the Fat Pipe as lots of replies were coming in.
…
This happened to me about 5 or 6 times this morning reading the Pipe. I assumed it was a bug from todays system upgrade.
…
i am investigating more this morning, and wheat seems to be happening is that embedded X posts within a thread will just spontaneously reload. When it happens, it appears to be all of the ones that are close to the area in focus. That is what causes the scrolling and placement issues. It seems to happen only when scrolling. Not sure if this helps, but just trying to track down more details.
I have not been able to reproduce the issue on my computer, yet lots of people are complaining about it, and several have specifically said it started after the update (although I have no way of confirming this right now).
Any ideas of help would be appreciated. Thanks.