Element shows ping when a message with `@room` is deleted

[SethFalco]

Steps to reproduce

1. Be in a room where notifications settings are set to All messages.
2. Another user sends a message in that room. (Will trigger notification.)
3. That same other user deletes their message. (Will trigger another notification.)

Outcome

What did you expect?

I should get notified for the message with @room. However, I should not receive any notification for the deletion of that message.

What happened instead?

I got pinged twice. Once when the message is sent, and again when the message is removed. The second ping only appears in Element, it doesn't send the notification through to my OS.

Operating system

Debian 13 (Trixie)

Application version

Element version: 1.11.110 Crypto version: Rust SDK 0.13.0 (f64839e), Vodozemac 0.9.0

How did you install the app?

https://element.io/download#linux

Homeserver

one.ems.host

Will you send logs?

Yes

Context

I've written a Matrix bot that just pings everyone in the room and announces when one of us goes live on Twitch. It then deletes the message when the streamer goes offline.

For Element users, I've found this is actually causing users to get pinged when the streamer goes offline, which doesn't seem intended. There wouldn't be much benefit to ping a user about a deleted message.

[t3chguy]

Cannot reproduce this

https://github.com/user-attachments/assets/ef67389f-8e15-4e70-ac1a-336ae6d148e3

[SethFalco]

Strange, I'll attach a video too. Turns out the issue isn't just with @room either.

https://github.com/user-attachments/assets/301c9263-71fd-4c36-af95-449de3fac528

I've noticed that it doesn't happen if I have the room on my default notification settings. If I hover over the room and set the notification settings to "All messages" it does happen, but on "Match default settings" it does not.

I've amended the steps to reproduce accordingly.

[t3chguy]

That'll be just how Matrix push rules work, setting a room to All messages sets up a room-specific push rule https://spec.matrix.org/v1.16/client-server-api/#push-rules which matches all events in that room which aren't treated by any other push rule and there is no predefined rule which matches redactions to avoid them landing on the new room-specific pushrule. https://spec.matrix.org/v1.16/client-server-api/#predefined-rules