2 added 725 characters in body
source | link

For the very narrow range of questions this would be useful for, couldn't spoilers simply be obfuscated using ROT13? It worked for newsgroups..

Another idea for a workaround, utilise the code-block overflow:auto property:

Spoiler -->                                                                                                  Not really, this is just an example

If a "proper" spoiler tag is to be implimented, I think the most important part of this is codinghorror's response:

isn't there a HTML tag that we could set a CSS style on to work this way?

..so is deciding on a markdown representation. For example, prefixing each line with "! ", the same way block-quotes use "> "

> This is a block quote,
> using current syntax

..but, the following is a spoiler!

! This is a spoiler,
! using a new syntax

The biggest problem with making a new "spoiler" syntax would be sites using the data-dump for whatever reason would have to implement it also.. Currently the posts are standard, nice and simple markdown, and I think it's better this way..

For the very narrow range of questions this would be useful for, couldn't spoilers simply be obfuscated using ROT13? It worked for newsgroups..

Another idea for a workaround, utilise the code-block overflow:auto property:

Spoiler -->                                                                                                  Not really, this is just an example

For the very narrow range of questions this would be useful for, couldn't spoilers simply be obfuscated using ROT13? It worked for newsgroups..

Another idea for a workaround, utilise the code-block overflow:auto property:

Spoiler -->                                                                                                  Not really, this is just an example

If a "proper" spoiler tag is to be implimented, I think the most important part of this is codinghorror's response:

isn't there a HTML tag that we could set a CSS style on to work this way?

..so is deciding on a markdown representation. For example, prefixing each line with "! ", the same way block-quotes use "> "

> This is a block quote,
> using current syntax

..but, the following is a spoiler!

! This is a spoiler,
! using a new syntax

The biggest problem with making a new "spoiler" syntax would be sites using the data-dump for whatever reason would have to implement it also.. Currently the posts are standard, nice and simple markdown, and I think it's better this way..

1 Post Made Community Wiki
source | link

For the very narrow range of questions this would be useful for, couldn't spoilers simply be obfuscated using ROT13? It worked for newsgroups..

Another idea for a workaround, utilise the code-block overflow:auto property:

Spoiler -->                                                                                                  Not really, this is just an example