[Story] Reply to a message that contains a mention

[VolkerJunginger]

Story

As a user I want to be able to reply to a message that contains a mention.

Figma link: TBD

Acceptance criteria

• The design of the reply could take the mention into account.
• The reply should not to trigger notifications or badges for the mentioned user. (the user has already been mentioned for that message)
• The user can add an additional mention to their message

Size estimate

S

Open questions

Tasks

Beta Give feedback

1. The reply should not to trigger notifications or badges for the mentioned user is not aligned with MSC3952 Answered here

Subtasks

Android

Beta Give feedback

1. Mentions: Display mentions in replies vector-im/element-x-android#1456
   A-Pills A-Timeline T-Enhancement +3

iOS

Beta Give feedback

1. Mentions: Display mentions in replies vector-im/element-x-ios#1831
   A-Pills A-Timeline T-Enhancement +3

Rust

Beta Give feedback

1. Implement MSC3952: Intentional mentions matrix-org/matrix-rust-sdk#2606
   A-Notification A-Room-List A-Timeline X-Needs-Rust Z-Schedule +5
   

• QA signoff on completion
• Design signoff on completion
• Product signoff on completion

[manuroe]

The reply should not to trigger notifications or badges for the mentioned user is not aligned with MSC3952 that states Clients should include the sender of the event being replied to as well as any mentioned users in that event (excluding yourself)

@VolkerJunginger can you align with @daniellekirkwood on this acceptance criteria. Web and mobiles must have the same behavior.

[clokep]

@VolkerJunginger can you align with @daniellekirkwood on this acceptance criteria. Web and mobiles must have the same behavior.

I think MSC3952 was mostly designed to not change behavior. The behavior of the legacy mentions was that both the sender of the original message and the mentioned user in it would end up in the "fallback" text causing both to be mentioned.

Luckily MSC3952 makes it so you can control the fallback separately from who is mentioned, so this is actually controllable now.

[manuroe]

Thanks @clokep. This is great. This is then a product decision to make the break with legacy apps or other matrix clients.

@VolkerJunginger the thing to get here is this is the sender app that decides the people to mention. EX can send mentions as you describe but there will no way to prevent a different behavior from messages coming another matrix client.

[Velin92]

Thanks @clokep. This is great. This is then a product decision to make the break with legacy apps or other matrix clients.

@VolkerJunginger the thing to get here is this is the sender app that decides the people to mention. EX can send mentions as you describe but there will no way to prevent a different behavior from messages coming another matrix client.

according to @jplatte the intentional mention task can allow us to not to trigger notifications or badges for the mentioned user

[jplatte]

Just to be clear, intentional mentions help when the client that sends the reply implements them. The problem will persist for messages received by EX that are sent by clients that don't implement intentional mentions. (what Manu said above)

[VolkerJunginger]

Thanks @clokep. This is great. This is then a product decision to make the break with legacy apps or other matrix clients.

@VolkerJunginger the thing to get here is this is the sender app that decides the people to mention. EX can send mentions as you describe but there will no way to prevent a different behavior from messages coming another matrix client.

that's ok.

[Velin92]

Blocking element-hq/element-x-android#1456 and element-hq/element-x-ios#1831 since we need to decide if we want or not to display mentions as pills inside replies.
@callumu @VolkerJunginger