-
-
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
Read marker updates cause notifications #25849
Comments
@HarHarLinks Thank you for opening an issue. Unfortunately there is not enough information there for me to be able to reproduce it. Please update the description with steps/screenshots/video/more details so our developers can have a look at it. Can you send the output of the notifications debug (dev tools → notifications debug) in addition to a rageshake? You can access the dev tools from the room context menu without opening the room, if development mode is enabled. Then I can have a look if I can find something about the room or event in the logs. |
It was happening all the time this morning, even confirmed by another user, but I have trouble repro-ing on Element version: cc8afed-react-e33a7e41a441-js-29b815b6781d Olm version: 3.2.14. I guess I can close this until it returns. Rageshake was submitted alongside this report. I don't understand how the notifications debug info can be useful as I have to be in the room which means the notification gets resolved while I open the debug menu. |
derp, thanks TIL. I guess spelling out the reasoning to open it this way would have helped me understand :) |
Steps to reproduce
Outcome
What did you expect?
No notifications for read markers
What happened instead?
Unread markers everywhere
Operating system
arch
Browser information
Firefox 115.0.2
URL for webapp
develop.element.io
Application version
Element version: cc8afed-react-c57a4cb09090-js-de7959de6c5c Olm version: 3.2.14
Homeserver
matrix.org
Will you send logs?
Yes
The text was updated successfully, but these errors were encountered: