A user seeks to whitelist a class or attribute in a theme to target a carousel component, initially trying dir attributes but facing issues with text direction and security. The discussion reveals that themes cannot currently whitelist custom classes or attributes, and modifying the markdown pipeline requires a plugin. The team considers adding data-theme-* attributes to div elements as a solution, with a PR submitted to implement this. Other suggestions include using data-custom-* or data-c-* to avoid conflicts, and the idea of using HTML5 aside elements is also explored. The conversation highlights the limitations of the current whitelister and the need for a more flexible DSL to support theme-specific attributes. Johani shares their findings on dir and data-* attributes, while sam and riking discuss potential solutions and naming conventions. Johani submits a PR to add data-theme-* to div, and bekircem asks about applying this to p tags.
Oh you can not do that yet, what I would like to do is just have .theme-[a-z]+ automatically whitelisted, but it requires fiddling with the whitelister a bit.
Assigning this to me, but may take a few weeks to get around to it.
If @angus or @david feel like giving it a shot, be my guest.
Yeah if you are trying to amend the markdown pipeline I think you need a plugin. One thing that is good security wise with themes is that they are not allowed to run on the server, this would change it.