Filip/matrix-spec
1
0
Fork 0
mirror of https://github.com/matrix-org/matrix-spec synced 2026-02-01 20:13:43 +01:00
Code Issues Actions 1 Packages Projects Releases Wiki Activity

moved client spoiler conversion to potential issues

Browse source
This commit is contained in:
Sorunome 2019-06-25 16:19:29 +02:00
parent 26349417ba
commit 4f83cc1c24
No known key found for this signature in database
GPG key ID: 63E31F7B5993A9C4
1 changed files with 4 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

8
proposals/2010-spoilers.md
View file

@ -52,10 +52,6 @@ however that wouldn't be HTML-compliant.
Instead of limiting the proposed `data-mx-spoiler` attribute only to the `<span>`-tag it could be
added to all tags, however it might make implementations for clients more complicated.
Clients would have to come up with a way how to input spoilers. This could be done, for example,
by adding a custom markdown tag (like discord does), so that you do `Text ||spoiler||`, however
that doesn't take a spoiler reason into account.
## Potential issues
Depending on context it might make sense to put other events, such as `m.image`, into spoilers,
too. This MSC doesn't address that at all. Using
@ -63,5 +59,9 @@ too. This MSC doesn't address that at all. Using
This MSC doesn't take HTML block elements into account.
Clients would have to come up with a way how to input spoilers. This could be done, for example,
by adding a custom markdown tag (like discord does), so that you do `Text ||spoiler||`, however
that doesn't take a spoiler reason into account.
## Security considerations
The spoiler reason needs to be properly escaped when rendered.