Is it even possible to [spoiler] a quote?

tar

[spoiler]

HAHA Wow , discourse is especially shitty these days!
[/spoiler]

Discosuccess! (that means "I failed")...

tar

Why is this software so relentlessly terrible?!

NedFodder

i'll go with the decision to allow this bastard mix of markdown, bbcode, and html. The Discodevs should have known there was no way to get that right. Since there's no spec, there's no way to write the correct tests, hence no way to write the correct code.

Wait, I'm buttuming they write tests, my bad.

NedFodder

[spoiler]

HAHA Wow , discourse is especially shitty these days!

[/spoiler]

[spoiler]

HAHA Wow , discourse is especially shitty these days!

[/spoiler]

[spoiler]
Adding a blank line doesn't work either.
[/spoiler]

Zecc

[spoiler]Empty lines

break spoilers[/spoiler]

tar

[spoiler]
 ought to help with that

why the fuck should I need to do that?
[/spoiler]
Also:
[spoiler]
Spoiler breaks ALL FORMATTING The fuck!
[/spoiler]

Onyx

I understand why they did emoji. The way they spoiler text is to add a huge text-shadow, which wouldn't affect emoji.

Hold on, don't tell me there's no better way? BRB, googlin' CSS trickery.

Onyx

https://jsfiddle.net/tp82xmv3/

THIS WAS HARD!

Fucking hell. How long did it take?

8 minutes. Including googling, forgetting how to use JSFiddle and messing up and fixing my JavaScript. Three times.

To clarify: This should work on emoji mixed with text as well, making my "excuse" above pointless.

tar

To be fair, if it took you 8 minutes, it probably means it would take the Discodevs 8 days to get halfway there.

aliceif

One second ...

[spoiler]
@(9) said:

I am the [b]strongest[/b]!

[/spoiler]

Fuck, every single fucking toxic hellstew PHP Forum can do that. It's just fucking BBCode. Not rocket science. I think even Steam's weird community discussions can handle it.

Source of the broken stuff:

[spoiler]
@(9) said:<blockquote>I am the [b]strongest[/b]!</blockquote>
[/spoiler]

Onyx

Fuck you Discourse!
#ACHTUNG!
Do not run this in this thread! This script has an infinite loop problem triggered by something being tested here! It will lock up your browser / tab until it's fixed!

It does work, in principle:

$('.cooked p').each(function() {
    if($(this).text() == '[spoiler]') {
        var elem = this;
        while(true) {
            elem=$(elem).next();
            
            if($(elem).text() == '[/spoiler]') {
                $(elem).remove();
                break;
            }
            else {
                $(elem).wrap('<div class="tdwtf-spoiler" style="-webkit-filter: blur(10px)"></div>');
                elem=$(elem).parent('.tdwtf-spoiler');
            }
        }
        $(this).remove();
    }
});

Yes, ACHTUNG!, as per this

tar

@Onyx said:

This script has an infinite loop problem triggered by something being tested here!
        while(true) { /*...*/ }

O_#

Onyx

Yes, I know, Tampermonkey was REALLY objecting to me assigning stuff inside while.

Or... wait...

Never mind, unrelated bug...

Let me see if I can fix this thing now that I can write a proper loop...

Onyx

I was buttuming Discourse is sensible... BIG mistake. There we go, proof of concept:

$('.cooked p').each(function() {
    if($(this).text() == '[spoiler]') {
        var elem = this;
        while($(elem).next().text().indexOf('[/spoiler]') < 0) {
            elem=$(elem).next();
            $(elem).wrap('<div class="tdwtf-spoiler" style="-webkit-filter: blur(10px)"></div>');
            elem=$(elem).parent();
        }
        $(elem).next().text($(elem).next().text().replace('[/spoiler]', ''));
        $(this).remove();
    }
});

There we go. It's far from perfect, doesn't do anything on click, and is extremely strict on [spoiler] tag formatting (exact matching, as you can see), but will spoiler whatever you feed it.

It's only a proof of concept anyway, this is in no way a proper fix. But I wanted to do it, just out of pure spite.

Also, it's missing the blur filter for FF. Meh.