Is it important for open to be a “bare” attribute (not sure of the
official name) like “<details open>” as opposed to “<details
open="open">”?
The latter form is already supported (in fact the second
“open” can be any string). Just add
#+attr_html: :open any-string-you-want
I know, but I did not test that.. just thought of doing as in that example in the mozilla documentation.
That's why I am using (org-element-property :attr_html special-block) in the code to get the raw values to #+attr_html.
The only thing I know off the top of my head is that CSS can be quite
hairy,
Heh, of course :)
so I would not be surprised if this wrapper is sometimes needed.
And indeed, support for it would be missing.
Is it something that is
likely to crop up for other elements as well, such that it would be
desirable to support it in org core?
That would be great. I myself wasn't sure if I should bring that up to Org core.. I had just implemented #+attr_css support for ox-hugo.
It looks like this:
#+attr_html: :class red-text
#+attr_css: :color red
- Red list item 1
- Red list item 2
Above will generate <style .red-text { color: red; } </style><div class="red-text">..</div>, with that list in the div.