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

'All Messages (loud)' setting considers room avatar change and leaves stuck notification #3561

Open
turt2live opened this issue Apr 3, 2017 · 1 comment
Labels
A-Avatar A-Notifications P2 S-Minor Impairs non-critical functionality or suitable workarounds exist S-Tolerable Low/no impact on users T-Defect

Comments

@turt2live
Copy link
Member

turt2live commented Apr 3, 2017

Description

While setting up a new room (with no messages) I intentionally set the notification level to 'All Messages (loud)'. Another user changed the room avatar and that caused an audible and visual notification that now can't be removed.

Unsure if this applies to any other case besides this specific case, so the reproduction steps are for this known case. Possibly related to #3363.

Edit: Sending a message after the notification will allow you to clear the notification

Steps to reproduce

  • Create a new room and invite someone to it
  • Set your notification setting to 'All Messages (Loud)'
  • Be active in another room while the someone you invited sets the room avatar
  • Note audible notification and visual indicator on room

I would have expected silence. The room doesn't record a 'room avatar changed' event and it's unclear as to why I got the notification. Not to mention I can't dismiss the notification.

Log: not sent (unable)

Hopefully helpful but probably just excess filler screenshots:
image
image
(avatar changed after invites)

Version information

  • Platform: web (in-browser)
  • Browser: Chrome 56
  • OS: Windows 10
  • URL: riot.im/develop
@lukebarnard1
Copy link
Contributor

lukebarnard1 commented Apr 4, 2017

WRT the notif not disappearing: I bet this has something to with the membership EventListSummary (MELS) at the bottom. Maybe a read receipt can't be sent for the most recent event because it's been hidden by the MELs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-Avatar A-Notifications P2 S-Minor Impairs non-critical functionality or suitable workarounds exist S-Tolerable Low/no impact on users T-Defect
Projects
None yet
Development

No branches or pull requests

5 participants