Ihor Radchenko <yanta...@posteo.net> writes: > We are discussing the way Org formats HTML tags in HTML export. > Some of the tags added by Org are simply bare tags, like <br /> below. > > <li><a id=".."></a>Low-level heading<br /> > > The suggestion is to add a unique class to each tag produced by Org HTML > export, so that CSS rules can precisely target various tags.
We have been waiting for 2 months, but nobody seems to be interested enough in the topic to participate. Closing the poll. Closed. So, it has to be my call. I suggest the following: 1. Create a function similar to `org-html-close-tag', but accepting attributes as an alist. 2. Introduce a custom option controlling which tags should be assigned classes 3. Change all the users of `org-html-close-tag' and places that directly produce HTML tags to use the new function By default, nothing should change. But I will not object an alternative default that will assign classes everywhere. -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at <https://orgmode.org/>. Support Org development at <https://liberapay.com/org-mode>, or support my work at <https://liberapay.com/yantar92>
