Post

So here's an interesting little thing or 2 @nomster.bsky.social , @foolip.org , and myself have been cooking up—along with lots of help from others!: developer.chrome.com/blog/declara... This could lead to some VERY interesting changes in how we write web pages. Would love to hear your thoughts!

developer.chrome.comDeclarative partial updates  |  Blog  |  Chrome for DevelopersLearn about new out-of-order streaming capabilities and the renewed HTML insertion and streaming methods available for testing from Chrome 148

26 reposts83 likes

This originally started using actual HTML elements as you can see in the history of the explainer. This was discussed extensively as part of standardisation. E.g. github.com/whatwg/html/... PIs offer many benefits, including being able to slot in sections without altering the DOM with a container.

github.comUpcoming WHATNOT meeting on 2026-01-08 · Issue #12034 · whatwg/htmlWhat is the issue with the HTML Standard? Today we held our weekly triage call (#12015) and the meeting notes are posted there. The next one is scheduled for January 8th, 2026, at 9AM PDT. Note tha...

I have chosen, many moons ago, to only use technologies supported by all 3 browser vendors Done my tour of duty in Mosaic, Netscape days Got the scars from pre-jQuery days I read the .dev post, looks interesting, but technology only works when y'all co-operate, not just because something is cool.

Oh there’s been a lot of cooperation on these and we’ve got a lot of feedback and positive signals from other browser vendors. There are PRs open to add them to the relative specs (HTML and the like) and we expect those to land soon. At which point we’ll ship it unflagged!

No ETA on when it will actually land in other browsers though, but someone has to go first and we’re happy to take that on. The important thing is we have good consensus on these (that doesn’t always happen, but we try!). And in the meantime we’ve released some polyfills to help with that.

@react.dev/facebook told our team years ago that they’d only use this kind of thing if they could synchronize updates so it wasn’t like “popcorn” randomly popping into the page. Does The API support that? Templates can be small like items in a list. Did you picture the API being used on page load?

Yeah this would be incredible! If you want a super simple way to try it out I built a jsx framework for streaming HTML. You can just use generator fns to yield the marker, await some task, then stream in the rest without client js. ovrjs.com

Cool, article, one point of clarification: > A common pattern popularized by frameworks like Astro and React is the island architecture where components are hydrated independently on top of static HTML. React never implemented islands and were explicitly against the idea.

to be fair, it was always very easy to implement "islands" yourself with React. the whole concept of "hydration" did not exist before in any framework – that's what initially drew me to it. remember "isomorphic" components? 😅

Credit goes to Katie Sylor-Miller for coming up with the idea, Jason for writing the article that inspired a lot of people, and Astro for implementing a popular framework around it.

Dumb questions that I can’t remember the answers to: 1. Can the template contain JS that will execute upon insertion? 2. Can the template be in the DOM before the referenced PI is? Very nice though! Been watching this for a while!

Put another way: is the order that the PI must always come first and then the template? Or (for whatever reason) can the template come first and then the PI?