<p>
<em>Some <?start name="hl"?>text</em>
to replace<?end name="hl"?>.
</p>
Jake Archibald at Mozilla has a good video about this. https://www.youtube.com/shorts/yARSOcqOWvY <p>
<em>Some replaced text
</p>
Which, by the HTML standard, will automatically close the `</em>` as the `</p>` closes.That's really really really awful
Well, you're allowed to write it, but the browser will just ignore the <?end> marker. The range will end at the </em> tag, the same place https://github.com/WICG/declarative-partial-updates/blob/mai... says it goes by default if you don't write the <?end> at all. (That default wouldn't make a ton of sense if patch ranges were allowed to break out of their parent elements like this.)
Jake Archibald thinks it'd be cool to use a similar syntax to do CSS highlights, but there are other problems with that (like not being able to create overlapping ranges), and he's not on the Chrome team that's pushing this proposal.
Well yes, because no better technology existed. I don't see what kind if experience proved that writing a million imperative ad-hoc solutions for out-of-order loading would be better than a standardized solution.
Probably to not break anything in older browsers which hasn't adopted it yet: new tag will be simply ignored, that's my thinking
> I'm amazed that they even put this in chrome, let along are saying things like "let sites use this new functionality right away even before this lands in other browsers"
It is behind the flag, like every other new proposal they made. Even though some dev would like to use it right now (for regular site visitors, not for self testing), she can't.
As an aside, I’m still rather annoyed that web components use hyphens. I really thought colon’s and namespaces made perfect sense there.