From 4f83cc1c244b78d9c34abde492116f4dcdae4047 Mon Sep 17 00:00:00 2001 From: Sorunome Date: Tue, 25 Jun 2019 16:19:29 +0200 Subject: [PATCH] moved client spoiler conversion to potential issues --- proposals/2010-spoilers.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/proposals/2010-spoilers.md b/proposals/2010-spoilers.md index 40feed29..fc470fcc 100644 --- a/proposals/2010-spoilers.md +++ b/proposals/2010-spoilers.md @@ -52,10 +52,6 @@ however that wouldn't be HTML-compliant. Instead of limiting the proposed `data-mx-spoiler` attribute only to the ``-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.