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

weird receipts (m.read) behavior #12265

Closed
PhilipHomburg opened this issue Feb 6, 2020 · 1 comment
Closed

weird receipts (m.read) behavior #12265

PhilipHomburg opened this issue Feb 6, 2020 · 1 comment

Comments

@PhilipHomburg
Copy link

For rooms that I follow, I switch to the room and then click on the up arrow with the green dot to continue reading where I left off.

What riot-web does is first set m.read to the most recent event (clearing the unread event counter on the way) as soon as I look at the room. Then the up arrow jumps to m.fully_read.

Note that to other people in the same room, this gives the impression that I read the entrie room, even when I just look at the screen long enough to find the up arrow.

My preference would be to have an option that jumps to m.fully_read (or even m.read) when switching to a room instead of the most recent event. The down arrow makes it easy enough to reach the most recent event.

Alternatively, if showing the most recent events first is preferred, maybe delay setting the m.read pointer for 10 seconds to allow a user who wants to read the entire room to click the up arrow.

@t3chguy
Copy link
Member

t3chguy commented Feb 6, 2020

@t3chguy t3chguy closed this as completed Feb 6, 2020
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