Threads timeline can be completely misordered.

[ara4n]

Steps to reproduce

1. Click on a long thread in the thread panel to read it. It loads the last N messages of the thread
2. Switch room
3. Switch back again
4. The thread paginates in the previous N messages of the thread, but appends them rather than prepends them to the thread timeline - or something similarly whacky. As a result, you end up with the pages out of order for the thread. Switching thread and back again fixes it.

Outcome

What did you expect?

Reliable thread ordering.

What happened instead?

Some kind of race between thread-pagination and thread-load which means the old page loads before the new page.

I don't have logs, but will rageshake when it next happens, which is roughly 30% of the time when loading a long thread.

Operating system

No response

Application version

nightly

How did you install the app?

No response

Homeserver

No response

Will you send logs?

No

[ara4n]

i keep getting this, whenever i view a thread i haven't seen before by tapping on it in the main timeline when the timeline panel was closed. the root msg ends up in the middle of the thread; the newer messages are then above it and older msgs below it. so the order is something like 5,6,7,8,1,2,3,4.

[anoadragon453]

I've just seen this, after being linked to a message in a thread. I was fairly confused until I noticed the timestamps!

I've sent a rageshake.

[davidegirardi]

Same is happening to me in a thread. No way to fix it apparently. Happens both on Nightly and production. I rageshook.

[estux]

This bug drove away some people from Element in my team (back to WA), as it's still standing and hitting us (apparently) randomly.