archive
/
matrix-spec
mirror of https://github.com/matrix-org/matrix-spec
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

fix typo

Browse Source
pull/2227/head
Tol Wassman 2 months ago committed by GitHub
parent fda3be5ee3
commit fca945c8ac
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File

6
content/client-server-api/modules/rich_replies.md
Unescape Escape View File

@ -20,9 +20,9 @@ Previously, a rich reply could only reference another `m.room.message` event.
{{% boxes/note %}} {{% boxes/note %}}
{{% changed-in v="1.13" %}} {{% changed-in v="1.13" %}}
In previous versions of the specification, rich replies could include a fallback In previous versions of the specification, rich replies could include a fallback
representation of the original message message in the `body` (using a prefix representation of the original message in the `body` (using a prefix sequence)
sequence) and `formatted_body` (using a custom HTML element) for clients that do and `formatted_body` (using a custom HTML element) for clients that do not
not support rich replies. This is no longer the case, but clients SHOULD still support rich replies. This is no longer the case, but clients SHOULD still
remove this fallback before rendering the event. remove this fallback before rendering the event.
To strip the fallback on the `body`, the client should iterate over each To strip the fallback on the `body`, the client should iterate over each

Write Preview
Loading…
Cancel
Save