Skip to main content

This is an interesting #HTML proposal from @Seirdy

Should there be a `<spoiler>` element?

https://seirdy.one/posts/2023/11/12/spoiler-element/

My heart says yes. HTML should reflect what people are actually doing on the web. How they write. The features they invent.

But my head says it is a duplicate of `<details>` albeit non-block level.


Proposal: an HTML element for spoilers

An informal proposal for dedicated elements for spoiler tags in HTML: use-cases, syntax, semantics, recommended UA behavior, and comparisons with “details”
Seirdy’s Home
#html @Seirdy
in reply to Terence Eden

Charlie
Charlie
• •
100% yes. The greatest failure of HTML is that it never followed behind real world usage, codifying common patterns. Even JS did this after letting jquery lead the way.
in reply to Charlie

Seirdy
Seirdy
• •
FWIW the ticket is here: https://github.com/whatwg/html/issues/9926

A spoiler element · Issue #9926 · whatwg/html

What problem are you trying to solve? A standard way to make content inaccessible and opaque to the user without consent, with optional preview text. More details on this proposal are in this artic...
GitHub
in reply to Terence Eden

Roma Komarov
Roma Komarov
• •

A related Open UI issue: https://github.com/openui/open-ui/issues/772

There are many nuances to spoiler-type things, aside from the inline-block level difference from details.


A standard spoiler / content-warning mechanism · Issue #772 · openui/open-ui

A spoiler / content-warning mechanism is used to hide content not all readers may wish to read or at least not yet. In addition to spoilers and content warnings, this can be used to tag the answer ...
GitHub
⇧