-
-
Notifications
You must be signed in to change notification settings - Fork 97
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
Remove reply fallbacks #1994
base: main
Are you sure you want to change the base?
Remove reply fallbacks #1994
Conversation
As per MSC2781. Signed-off-by: Kévin Commaille <[email protected]>
Signed-off-by: Kévin Commaille <[email protected]>
@@ -0,0 +1 @@ | |||
Remove reply fallbacks, as per [MSC2781](https://github.com/matrix-org/matrix-spec-proposals/issues/2781). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It should probably be a *.removal
changelog, but given that the generated heading says "Endpoints Removed", it is not quite right.
Signed-off-by: Kévin Commaille <[email protected]>
In previous versions of the specification, [rich replies](#rich-replies) could | ||
use a special tag, `mx-reply`, this is no longer the case. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Doesn't this need to mention that it should always be stripped still?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, I added a sentence here.
replies, this is no longer the case. Clients might still want to remove this | ||
fallback before rendering the event. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think they must remove it, no?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There is not must in the MSC. There is:
Clients […] should consider treating
<mx-reply>
parts as they treat other invalid html tags.
And
[…] clients may need to strip out such fallbacks.
Signed-off-by: Kévin Commaille <[email protected]>
As per MSC2781.
Pull Request Checklist
Preview: https://pr1994--matrix-spec-previews.netlify.app