# What could a "spoiler tag" extension look like?

**URL:** <https://talk.commonmark.org/t/what-could-a-spoiler-tag-extension-look-like/767>\
**Category:** Extensions\
**Created:** [October 6, 2014, 4:05am UTC](https://talk.commonmark.org/t/what-could-a-spoiler-tag-extension-look-like/767 "2014-10-06T04:05:05Z")\
**Posts on this page:** 1\
**Showing post:** 80

<div class="post-metadata">

**Author:** ![codinghorror](https://talk.commonmark.org/user_avatar/talk.commonmark.org/codinghorror/32/2_2.png) [@codinghorror](https://talk.commonmark.org/u/codinghorror)\
**Post date:** [February 8, 2019, 6:12am UTC](https://talk.commonmark.org/t/what-could-a-spoiler-tag-extension-look-like/767/80 "2019-02-08T06:12:46Z")

</div>

@jgm just to put some perspective on this, I’ve been surprised how often spoilers come up in typical internet posts. It may not be big in the Pandoc audience, but I assure you, for more non-techie conversational topics, spoilers come up _wayyy_ more than I ever thought they would. They come up _a lot_.

I’d still get tables in first, but spoilers is certainly in my top 3 of potential markdown extensions that people actually _use_ and ask for.

Heck you can kinda see that in how pervasive “rolling your own syntax” is for this use case! And it kinda sucks that they’re all over the place, no two sites seem to do it the same way 😕

---

_[View the full topic](https://talk.commonmark.org/t/what-could-a-spoiler-tag-extension-look-like/767)._
