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

Edited thread response cause an intentional mention to the sender of the thread's root #28690

Open
bnjbvr opened this issue Dec 9, 2024 · 0 comments
Labels
A-Message-Editing 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

@bnjbvr
Copy link
Member

bnjbvr commented Dec 9, 2024

Steps to reproduce

  1. Send a message to a room
  2. Have somebody else send a threaded response to that message, with no mentions at all in it
  3. Have them then edit their threaded response, still with no mentions in it

Outcome

What did you expect?

No mentions

What happened instead?

I get mentioned

Operating system

Archlinux

Browser information

latest Firefox Dev Edition

URL for webapp

https://develop.element.io/

Application version

Element version: 0130443-js-cf39595bd7a6 Crypto version: Rust SDK 0.7.2 (517d99b), Vodozemac 0.7.0

Homeserver

element.io

Will you send logs?

No

@bnjbvr bnjbvr added the T-Defect label Dec 9, 2024
@dosubot dosubot bot added A-Message-Editing 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 labels Dec 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-Message-Editing 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

1 participant