5

In a recent question of mine, I encountered what I think is a bug when I tried to put a regular blockquote between two spoilers:

Text:

!This is spoiler 1.

"This is the regular blockquote".

!This is spoiler #2.

As you can see, it renders everything as one big blockquote as well as the exclamation points that are supposed to make something a "Spoiler". Trying to make the middle blockquote into a spoiler, resulting in three sooilers in a row, also fails.

!Spoiler 1

!Spoiler 2

!Spoiler 3

It happens on both the mobile site and the full site.

1
  • 2
    Spoiler blocks aren't fully implemented by design so you'll find a lot of strange goings on with them.
    – TheLethalCarrot Mod
    Commented Aug 19, 2019 at 10:29

2 Answers 2

Reset to default
8

This is spoiler 1.

"This is the regular blockquote".

This is spoiler #2.

Is this what you want?

Code for the above:

>!This is spoiler 1.

<!>

>"This is the regular blockquote".

<!>

>!This is spoiler #2.
11
  • @Spencer I just put a non-displayed entity in between, such as <!>
    – Alex
    Commented Aug 18, 2019 at 2:33
  • 2
    @Alex I remember once someone on Main Meta got quite annoyed at me for doing that; this kind of stuff seems to be frowned upon.
    – Stormblessed
    Commented Aug 18, 2019 at 3:29
  • @Stormblessed Why?
    – Alex
    Commented Aug 18, 2019 at 3:36
  • 2
    @Alex I don’t know, ask Sonic the Anonymous whatever.
    – Stormblessed
    Commented Aug 18, 2019 at 3:40
  • 6
    @Stormblessed Just because Sonic doesn't like something, doesn't mean it's "frowned upon" in general.
    – Rand al'Thor Mod
    Commented Aug 18, 2019 at 15:25
  • 2
    @Spencer I've edited Alex's answer to add the code for how it was produced.
    – Rand al'Thor Mod
    Commented Aug 18, 2019 at 15:25
  • Looking at the emitted HTML, those <!> thingies seem to be producing empty <p> tags, which is semantically incorrect since a "paragraph" should contain text (but I'm really surprised that anyone would notice or care). I suppose a screen reader might mishandle them, but honestly, I'd expect them to either skip it or just say "paragraph no text" or something like that.
    – Kevin
    Commented Aug 20, 2019 at 2:24
  • @RandAlThor Thanks.
    – Spencer
    Commented Aug 20, 2019 at 9:36
  • @Kevin Maybe it should be something like <!/> then.
    – Spencer
    Commented Aug 20, 2019 at 9:37
  • @Stormblessed Also, if there's a specific discussion on 'main' or 'meta' then, try to link to it, otherwise it sounds like people's opinions and we'll simply ignore it.
    – Möoz
    Commented Aug 21, 2019 at 22:55
  • 1
    You can also use a HTML comment <!-- --> which will not be translated into anything.
    – Mr Lister
    Commented Aug 22, 2019 at 11:01
3

With the introduction of CommonMark this is now even easier to do, just use the following markdown:

>!This is spoiler 1.

>"This is the regular blockquote".

>!This is spoiler #2.

For the rendered output:

This is spoiler 1.

"This is the regular blockquote".

This is spoiler #2.

Continous spoilers still don't work, I don't think that has ever really been supported, but you can force it yourself like:

>!Spoiler 1
>! <br/><br/>
>!Spoiler 2
>! <br/><br/>
>!Spoiler 3

For:

Spoiler 1

Spoiler 2

Spoiler 3

2
  • Instead of fancy HTML tags (which the non-coders among us might not be familiar with), an easier method is simply to put two spaces at the end of each line within a continuous spoilerblock.
    – Rand al'Thor Mod
    Commented Aug 22, 2020 at 10:20
  • @Randal'Thor Good point didn't think about two spaces on the empty lines too
    – TheLethalCarrot Mod
    Commented Aug 22, 2020 at 10:22

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .