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

[Bug] Thread replies produce multiple duplicate notification when there's a line. #24700

Open
8227846265 opened this issue Mar 1, 2023 · 1 comment
Labels
A-Threads 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

@8227846265
Copy link

8227846265 commented Mar 1, 2023

Steps to reproduce

  1. User A creates a thread with --- on the first message.
  2. User B replies to thread
    image
  3. Windows generate a 6 duplicate notification even if User A didn't even reply to the thread.
    image

image

Outcome

What did you expect?

When I make a reply to a thread that has a line --- on the first message. It will not generate duplicate notifications out of nowhere

What happened instead?

It will generate duplicate notifications when you send a reply.

Operating system

Windows 11

Application version

Element version: 1.11.24 Olm version: 3.2.12

How did you install the app?

https://element.io/download

Homeserver

No response

Will you send logs?

Yes

@8227846265 8227846265 changed the title [Bug] Thread replies produce multiple duplicate notification. [Bug] Thread replies produce multiple duplicate notification when there's a line. Mar 1, 2023
@florianduros florianduros added S-Minor Impairs non-critical functionality or suitable workarounds exist O-Uncommon Most users are unlikely to come across this or unexpected workflow A-Threads labels Mar 1, 2023
@t3chguy
Copy link
Member

t3chguy commented Mar 1, 2023

Related #24620

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-Threads 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
Development

No branches or pull requests

3 participants