I can see two gotchas: 1. nesting adds some cost for browser renderers (might be negligible, though, worth testing) 2. it's additional complexity to consider when converting from other formats to HTML.
Replies
Great points but I feel like the cssom could handle it and the whole point of letting the browser figure it out is so that even the injected ad is semantic. I can see how that would throw off the depth styling though. Thanks.
aug 20, 2025, 5:43 pm • 1 0 • view
I think it would be fairly simple to implement at templating side now that I think of it. That would then compile to what current browsers expect. Maybe those boundaries would have to use some custom element that's compiled away. Here's my sort of related experiment: gustwind.js.org/templating/ .
aug 20, 2025, 5:51 pm • 1 0 • view
HTMLisp basically does this - HTML + LISP -> AST -> HTML. I guess what you are looking at is actually an AST transformation that's flattening the tree and removing the markers.
aug 20, 2025, 5:52 pm • 1 0 • view
Awesome. Yah most cms languages support transformation in some fashion. What I'm vying for is a W3c change to the html spec to include a tag.
aug 20, 2025, 6:14 pm • 1 0 • view