You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
janogarcia opened this issue
Jan 20, 2022
· 4 comments
Assignees
Labels
A-ThreadsO-FrequentAffects or can be seen by most users regularly or impacts most users' first experienceS-MinorImpairs non-critical functionality or suitable workarounds existT-DefectX-BlockedZ-Labs
Open the thread panel to browse the current thread list.
Start a new thread.
Outcome
What did you expect?
The new thread to be added to the topmost position of the thread list.
What happened instead?
It seems to go like this. When you first visit a room and are just browsing it, the order for threads is correct, but as soon as you create a new thread it gets added to the last position in the stack, instead of the topmost.
Operating system
No response
Browser information
No response
URL for webapp
develop.element.io
Application version
Element version: c40dbf1-react-f59ea6d7adf5-js-230e3b4acee3 Olm version: 3.2.8
Homeserver
matrix.org
Will you send logs?
No
The text was updated successfully, but these errors were encountered:
Bottom - New thread (posted @ 17:25) showing on the bottom of the list.
dbkr
added
O-Frequent
Affects or can be seen by most users regularly or impacts most users' first experience
S-Minor
Impairs non-critical functionality or suitable workarounds exist
labels
Jan 21, 2022
As discussed internally last week, this behaviour is quite tedious to implement for clients when dealing with a paginated API.
This is currently blocked on element-hq/element-meta#152 and the ordering will be based on the root thread rather than the last reply to a thread until we have a new sorting filter available server-side
daniellekirkwood
changed the title
New threads created go to the end of the thread list
New threads created go to the end of the thread list (Thread list ordering)
Mar 5, 2022
Web now orders thread by the last reply time. In the future we will want this sorting to be done by the server, but for now we can consider this issue resolved
A-ThreadsO-FrequentAffects or can be seen by most users regularly or impacts most users' first experienceS-MinorImpairs non-critical functionality or suitable workarounds existT-DefectX-BlockedZ-Labs
Steps to reproduce
Outcome
What did you expect?
The new thread to be added to the topmost position of the thread list.
What happened instead?
It seems to go like this. When you first visit a room and are just browsing it, the order for threads is correct, but as soon as you create a new thread it gets added to the last position in the stack, instead of the topmost.
Operating system
No response
Browser information
No response
URL for webapp
develop.element.io
Application version
Element version: c40dbf1-react-f59ea6d7adf5-js-230e3b4acee3 Olm version: 3.2.8
Homeserver
matrix.org
Will you send logs?
No
The text was updated successfully, but these errors were encountered: