Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New threads created go to the end of the thread list (Thread list ordering) #20654

Closed
janogarcia opened this issue Jan 20, 2022 · 4 comments
Closed
Assignees
Labels
A-Threads 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 T-Defect X-Blocked Z-Labs

Comments

@janogarcia
Copy link

Steps to reproduce

  1. Visit a room with threads.
  2. Open the thread panel to browse the current thread list.
  3. 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

@janogarcia
Copy link
Author

Top - Correct order

top

Bottom - New thread (posted @ 17:25) showing on the bottom of the list.

bottom

@dbkr 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
@germain-gg
Copy link
Contributor

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

@germain-gg
Copy link
Contributor

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

@janogarcia
Copy link
Author

@gsouquet Awesome. Thanks for coming up with a workaround!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-Threads 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 T-Defect X-Blocked Z-Labs
Projects
None yet
Development

No branches or pull requests

4 participants