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.

Sign up for GitHub

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 bottom

Using gitter, and it is always showing (1) in browser tab etc. Mark all as read not working #25638

Closed
scaddenp opened this issue Jun 20, 2023 · 2 comments
Closed

Using gitter, and it is always showing (1) in browser tab etc. Mark all as read not working #25638

scaddenp opened this issue Jun 20, 2023 · 2 comments
Labels
A-Notifications O-Uncommon Most users are unlikely to come across this or unexpected workflow S-Minor Impairs non-critical functionality or suitable workarounds exist T-Defect

Comments

@scaddenp
Copy link

Steps to reproduce

https://app.gitter.im/?#/room/#serenity-bdd_serenity-core:gitter.im/$w9qDn7T2oBpJ7ZKNe5_KLOZY623k-fmv6f5L9ImuRmg
is where I am having problem.

image

and
image

If I scroll up, I get to see "Jump to new Messages" and "Mark all as read" widgets on right. Jump to new messages doesnt take me to anything I havent read, and Mark all as read doesnt do anything

Outcome

I expect the Element icon on the browser to be clear and room indicator not to show any numbers

Nothing I do changes that. Updated to latest version, Cleared Cache and Reload.

Operating system

Windows 10

Browser information

Chrome 114.0.5735.134

URL for webapp

https://app.gitter.im/?#/room/#serenity-bdd_serenity-core:gitter.im

Application version

Gitter version: 1.11.34 Olm version: 3.2.14

Homeserver

homeserver

Will you send logs?

No
@weeman1337 weeman1337 added S-Minor Impairs non-critical functionality or suitable workarounds exist A-Notifications O-Uncommon Most users are unlikely to come across this or unexpected workflow labels Jun 21, 2023
@weeman1337
Copy link
Contributor

Thank you for reporting the issue @scaddenp . There are currently a bunch of issues under investigation around stuck notifications: #24392

The one you are mentioning specifically should be #24595

I am going to close this issue. You should track the other issues for updates on this topic.

@weeman1337
Copy link
Contributor

Duplicate of #24595

@weeman1337 weeman1337 marked this as a duplicate of #24595 Jun 21, 2023
@weeman1337 weeman1337 closed this as not planned Won't fix, can't repro, duplicate, stale Jun 21, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
A-Notifications O-Uncommon Most users are unlikely to come across this or unexpected workflow S-Minor Impairs non-critical functionality or suitable workarounds exist T-Defect
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@scaddenp @weeman1337