May 23, 2026
Chrome stirs the markup pot
API proposed by Chrome: Declarative partial updates
Chrome wants web pages to update themselves, and commenters are loudly asking: why
TLDR: Chrome is testing a new experimental feature that lets parts of a web page fill in later, which it says could make modern sites faster and easier to build. Commenters were mostly confused or skeptical, with many asking what problem this solves and whether Google is reinventing tools developers already use.
Google Chrome just floated a new way for websites to swap in bits of a page later, instead of making everything arrive in strict top-to-bottom order. In plain English: a site could show a placeholder like “Loading…” and then drop in the real content when it’s ready, with Chrome pitching it as a faster, cleaner way to build modern web apps. It’s coming as an experimental feature in Chrome 148, with polyfills promised so developers can try it elsewhere too.
But the real show was in the comments, where the mood swung from confusion to open disbelief. One of the biggest reactions was basically: isn’t this just htmx? Another camp went even harder, questioning why browsers are getting involved in page updates at all when websites already use JavaScript and background requests for this. Several readers sounded personally offended by the weird new markup, calling the proposal “very odd” and “the boldest choice,” which is polite internet-speak for what on earth is this syntax.
Then came the classic browser-politics subplot: is this a genuine web standard in the making, or just Google doing Google things? One commenter immediately asked whether Mozilla is on board, because nobody wants another “works great in Chrome, good luck everywhere else” situation. The funniest reaction may have been the bluntest: “Wtf?” That pretty much summed up the thread’s energy—less “wow, the future” and more “please explain this to me like I’m not trapped in a standards meeting.”
Key Points
- •The article presents Chrome's proposed Declarative Partial Updates as a way to deliver and insert HTML in a less linear fashion.
- •It argues that HTML's in-order, top-to-bottom delivery model can create performance and development limitations for modern web applications.
- •The proposal includes two API groups: out-of-order HTML streaming in documents and new JavaScript APIs for easier dynamic HTML insertion.
- •The features are available for developer testing in Chrome 148 behind the experimental web platform features flag, with polyfills available for broader use.
- •The article explains out-of-order streaming using <template> plus processing instructions such as <?marker>, <?start>, and <?end> to replace placeholders, show temporary loading content, and support multiple updates.