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

Option to mark all messages in a channel as 'read' #1042

Closed
raboof opened this issue Jun 30, 2023 · 3 comments
Closed

Option to mark all messages in a channel as 'read' #1042

raboof opened this issue Jun 30, 2023 · 3 comments

Comments

@raboof
Copy link

raboof commented Jun 30, 2023

Your use case

What would you like to do?

When a channel has many 'unread' messages, I would like to mark the entire channel as 'read'. This works fine with the 'mark all as read' 'little cross' in the top-right for 'regular' messages, but this doesn't clear unread messages that are inside of threads.

Why would you like to do it?

To get back to 0 unread-message markers

How would you like to achieve it?

I think it would make sense if the 'mark all as read' button would be shown also if there are unread messages in threads, and also mark those as read.

Have you considered any alternatives?

No response

Additional context

Tested on version 1.11.34

@t3chguy
Copy link
Member

t3chguy commented Jul 3, 2023

Not clearing things in threads is already fixed on develop and will be fixed in the next release.

@t3chguy t3chguy closed this as completed Jul 3, 2023
@raboof
Copy link
Author

raboof commented Jul 3, 2023

Awesome, thanks! Sorry about the noise, I didn't see the existing issue/PR/... (I did see element-hq/element-web#24595 but that seemed different)

@raboof
Copy link
Author

raboof commented Aug 18, 2023

I'm now on element-desktop version 1.11.38 (released two weeks ago) and I'm still seeing the behavior where the "Mark all as read" button does not mark unread messages in threads as read.

Am I missing something? Was this fixed in a component that didn't make it into 1.11.38 yet?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants