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

Read marker updates cause notifications #25849

Closed
HarHarLinks opened this issue Jul 26, 2023 · 4 comments
Closed

Read marker updates cause notifications #25849

HarHarLinks opened this issue Jul 26, 2023 · 4 comments
Labels
T-Defect X-Needs-Info This issue is blocked awaiting information from the reporter

Comments

@HarHarLinks
Copy link
Contributor

Steps to reproduce

  1. Send a message in a room
  2. Switch to another room
  3. Wait for the other person to read your message from 1.
  4. Watch the room from 1. be marked as unread
  5. If you have all notifications to noisy etc, receive notifications for it

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

@weeman1337
Copy link
Contributor

@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.

@weeman1337 weeman1337 added the X-Needs-Info This issue is blocked awaiting information from the reporter label Jul 26, 2023
@HarHarLinks
Copy link
Contributor Author

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.

@weeman1337
Copy link
Contributor

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.

Quote from above:

You can access the dev tools from the room context menu without opening the room, if development mode is enabled.

image

@HarHarLinks
Copy link
Contributor Author

HarHarLinks commented Jul 27, 2023

derp, thanks TIL. I guess spelling out the reasoning to open it this way would have helped me understand :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
T-Defect X-Needs-Info This issue is blocked awaiting information from the reporter
Projects
None yet
Development

No branches or pull requests

2 participants