Firefox for Web Developers @webdevs.firefox.com · Feb 16 HTML might be getting a new type of tag, which… hasn't happened this millennium. Here's the new syntax, and how it works:
300 likes 14 replies
Replies
Those PI markers for declaring ranges remind me of how Apache Wave (formerly Google Wave) annotated text for styling (also links and spellchecking). foo <?a "style/fontWeight"="bold" ?>bold <?a "style/fontStyle"="italic" ?>bold-italic <?a "style/fontWeight" ?>italic <?a "style/fontStyle" ?>bar
Naming is hard, apparently, because I can see this being confused with the marker pseudo-element that already exists. developer.mozilla.org/en-US/docs/W...
Is there any precedent for non-tree-abiding tags?
Ugh. Can we not?
What is this tag type called? <? marker> and <? range>.
You said your example causes a layout shift, but if you're streaming in HTML and the browser is laying out the first content would it be possible *not* to cause a layout shift?
the fact firefox has any AI integration is reason enough for me to never use it again, and for everyone to boycott it.
Being able to apply non-layout styling to arbitrary ranges (without JS) would be handy.
this would be really cool 👀 im currently using something similar for my website to do a very basic "SSR components" in rust with similar syntax <#foo>Lorem ipsum</#foo>
Wasn't <geolocation> recently added?
ooooo would this work as a back end for fragments in frameworks?
Here's the explainer on HTML patching github.com/WICG/declara...
Doesn’t harm to link to more of the relevant issues and explainers here, I guess.
I don’t see how riddling your content with markers to do syntax highlighting would fare any better than the span soup approach. I see more benefit in something like `<script type="highlightmap">` + `<pre highlightedby=highlightmap>` in which the browser would do it all by itself (+ is polyfillable)