HNHacker News
TopNewBestAskShowJobs

nomsternom

3 karma · joined May 24, 2026

submissionscomments
nomsternom··on API proposed by Chrome: Declarative partial updates
That's a valid opinion!
nomsternom··on API proposed by Chrome: Declarative partial updates
At the moment - you can treat it as a single "search & replace", and not as a replace all. And yes JS can do the rest atm. Hopefully introducing this (and processing instructions in general) can lead to additional enhancements in the future. But it would have to be gradual, kind of like how modern CSS evolved.
nomsternom··on API proposed by Chrome: Declarative partial updates
This would end up as:

<div> Here is some <em>HTML content</em>! <?marker name="placeholder"> <?marker name="placeholder1"> </div>

(only the first matching marker set is replaced.

nomsternom··on API proposed by Chrome: Declarative partial updates
Are you referring to the sentence about the polyfill? Seems like "shipping a polyfill for X before X lands in all browsers" is a reasonable thing to say? Donno
nomsternom··on API proposed by Chrome: Declarative partial updates
It's also a processing instruction rather than an element, which makes it possible to put it inside e.g. a <table> element and partially replace some rows.
nomsternom··on API proposed by Chrome: Declarative partial updates
Sure, but how is this related to out of order streaming?
nomsternom··on API proposed by Chrome: Declarative partial updates
(and this is correct, the start/end marker need to be siblings. You can't input something that starts in one parent and ends in another.)
nomsternom··on API proposed by Chrome: Declarative partial updates
Yea we've been working with Mozilla and Apple on that one as well but they haven't responded to the standards position yet. I am sure that we'll reach something that's within consensus.
nomsternom··on API proposed by Chrome: Declarative partial updates
How would that work? I think you posted something on the github but I don't think what you're conceiving here is possible with this API. It just reroutes HTML insertions from the template to a different location, there is no duplication.
nomsternom··on API proposed by Chrome: Declarative partial updates
Definitely an inspiration but less opinionated.
nomsternom··on API proposed by Chrome: Declarative partial updates
We've worked on the design closely together with Mozilla/Apple folks and with multiple external partners that want to use it.
nomsternom··on API proposed by Chrome: Declarative partial updates
How would you expect it to be in all the browsers before one of the browsers ships it first? We are seeking as much consensus as we can. It's an odd expectation.
nomsternom··on API proposed by Chrome: Declarative partial updates
We're working together with Jake on this. I do hope that processing instructions can help with highlights in the future.
nomsternom··on API proposed by Chrome: Declarative partial updates
It's expressed in terms of changing the output of where bides are inserted. Instead of new nodes being inserted to the template elements, they are inserted where the processing instructions were found.