-
-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Jump to unread displays in some improper circumstances #4180
Comments
@Autre31415 does the bar appear even when you've clicked the "X"? This feels related to https://github.com/vector-im/riot-web/issues/4134 |
The 'X' does get rid of it. |
OK, then it sounds like you're expecting it to disappear when you scroll down but it doesn't because you need to scroll quite slowly. If you click the "Jump to.." and then scroll down quickly, would you expect the banner to disappear? |
This isn't an issue that I've witnessed in prior versions of Riot. The jump to unread indicator has a tendency to pop up while I'm actively engaged in a conversation, and jumping to the first unread message will take it all the way back to when the conversation started even though I've been active in the conversation the entire time and no notifications have spawned. |
Right, so that sounds like a bug where the app's/view's read marker is not up-to-date with the server's. |
so, with 0.11.4 it's still on. this annoying pop up comes up quite often. clicking on it takes me back more than a day or days, even if the last message in room was sent by me few minutes ago. |
@4nd3r you can get rid of it by clicking "X".
This is expected behaviour
And so is this. If you are just finding the pop up annoying or unintuitive, see https://github.com/vector-im/riot-web/issues/4134 |
@lukebarnard1 I think I found the root cause. When more than 3 collapsed activities are present, you need to expand at least one of them for the read marker to consider it read. So even if you scroll down slowly, the read marker does not get updated and takes you far back to the first unread message every time since that cannot be marked as read unless you expand the collapsed messages. This is an issue in bridged rooms because IRC or Telegram bridges generate a lot of join/left or profile pic changed messages. |
I can almost never rely on "Jump to first unread message.". I have a simple 1-on-1 chat, where nobody leaves, changes names etc. Sometimes it takes me a week back. Half of the time it takes me back to my own message (it underlines my own message). It also takes me back to redacted events, closed a call events and so on. |
@TripleSnail, none of that is unexpected behaviour afaik - in reality we track the first unread event. If you send a message into the room and then leave your client reading messages into the room (without focusing on the window) your read marker will still be underneath the message that you sent - it was the last message you read. |
I had always understood, that it underlined the message that I had not read. Well, I guess everything makes more sense now. |
I see this message ALL THE TIME when I'm already current in a channel. Can we please get this back into the pipeline in some way? |
I see this message in chats pop up every so often even though i've seen all the messages already
OS: macOS Sierra
riot-web: 0.10.1
The text was updated successfully, but these errors were encountered: