# 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:** 31

<div class="post-metadata">

**Author:** ![mb21](https://cdn.commonmark.org/user_avatar/talk.commonmark.org/mb21/32/162_2.png) [@mb21](https://talk.commonmark.org/u/mb21)\
**Post date:** [October 29, 2014, 1:35pm UTC](https://talk.commonmark.org/t/what-could-a-spoiler-tag-extension-look-like/767/31 "2014-10-29T13:35:06Z")

</div>

> [@jgm](#):
>
> [this is some _inline_ content]{color=blue lang=en}

Indeed, as proposed in the [generic attributes thread](http://talk.commonmark.org/t/consistent-attribute-syntax/272), I like that syntax as well: it is basically a `span` element. It would be nice to have a corresponding `div` syntax. Using block quotes feels semantically wrong, and sometimes you might want the containing blocks to be parsed as well.

@jgm do you feel that the [proposed directives](http://talk.commonmark.org/t/generic-directives-plugins-syntax/444) are “overkill”?

---

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