Proposal: an HTML element for spoilers - @Seirdy : https://seirdy.one/posts/2023/11/12/spoiler-element/
@alilly 's response: https://www.alm.website/blog/2023-11-12-note-1
While I'd have no trouble adding support in Haphaestus, for Rhapsode's sake I back a request for a "topics" (or whatever you want to name it) attribute. As I've stated before both publicly & privately.
My issue is that in Rhapsode's UX any interactive control needs a textual label to be triggerable.
@alcinnz @Seirdy @alilly
don't we already have that in html with `<summary>` element? https://developer.mozilla.org/en-US/docs/Web/HTML/Element/details
@RyunoKi@layer8.space @alcinnz@floss.social @Seirdy@pleroma.envs.net @alilly@solarpunk.moe ah! Sorry. I shouldn't have missed that. The big technical difference, then, would be the ability to in-line a spoiler, which isn't possible with a details block. It also carries different semantics and is used differently.
I didn't actually read it....
@worldsendless @alcinnz @Seirdy @alilly The article compares it.
I can see a value in having an inline variant of it.