Display body in tombstone

[benparsons]

Your use case

What would you like to do?

If there is an body field available in the tombstone event, display it in place of the existing text.

Why would you like to it?

Because there may be a custom situation, where the normal text should be replaced.

How would you like to achieve it?

By honoring the body in the event.

Have you considered any alternatives?

No response

Additional context

No response

[anoadragon453]

Note that this field is specced as "A server-defined message" - https://spec.matrix.org/unstable/client-server-api/#mroomtombstone

So yes, it definitely should be shown.

[Palid]

Due to lack of spec compliance (and that it's pretty much frequent for all users) I'm bumping the priority up.

[Palid]

Moving down the priority after discussing with the team.

[turt2live]

The spec doesn't require this to be shown by the way. It's meant as a fallback for clients which don't do custom handling

[benparsons]

The spec doesn't require this to be shown by the way. It's meant as a fallback for clients which don't do custom handling

True but it would still be useful for Element to be able to (optionally) show this.

[turt2live]

Please not optionally 😭

Was just mentioning that the spec-compliance label was not correct - I personally think it should be shown (and has all kinds of use-cases for showing it).

[t3chguy]

Are we sure we want this? In the "happy path" this would add a spurious This room has been replaced which cannot be i18n'd to default Synapse tombstones.

Which seems very duplicative of the existing (i18n'd) text

[benparsons]

I would still like to be able to override the text.

What about if in the absence of text we used the i18n'd fallback?

[turt2live]

The server adds the text by default.

[t3chguy]

Yeah, the Synapse /upgrade API sets body to This room has been replaced without a way for the client to say not to, and it makes sense given the aforementioned purpose being

It's meant as a fallback for clients which don't do custom handling

[benparsons]

So, to get this feature we would need to make changes on Synapse and on Element? I still think it's a reasonable request to be able to display a custom text here, and we have customers who have use-cases for it.

[t3chguy]

Well the issue is, any worthwhile change you make on Synapse would break backwards-compatibility for clients which don't have explicit m.room.tombstone support - the client has no way of discerning the "default" fallback backwards-compat message from a more specific one