← Graph

Declarative Partial Updates

concept 4 connections

Experimental browser API — essentially Hotwire streams baked into the web platform. Uses HTML template tags with start/end markers to declaratively replace, append to, or remove named regions of the DOM as HTML streams down. Supports re-binding identifiers for continuous appends. Works great for out-of-order streaming of slow dashboard widgets. Currently JavaScript-only (few lines of code to wire it up, easily combined with View Transitions). Ryan's speculation: browsers could adopt this so a link or form submit with an opt-in attribute posts to the server, the server returns only the changed fragment, and the browser applies it — server-driven soft navigation with zero JavaScript. His demo email-signup form implements a polyfill and the whole UI runs on 614 bytes of JS. Chrome preview available behind flags; Ryan plans to push for browser adoption as his first browser API.

category
pattern
about
Declarative Partial Updates concept
Fifth and most forward-looking of the five APIs — Hotwire-like fragment streaming as a browser primitive.
about
Declarative Partial Updates concept
Ryan's answer points to this API as a future standardization of Turbo's model.
concept Declarative Partial Updates
related_to
Hotwire tool
Standardizes Hotwire's HTML-fragment-streaming model as a browser primitive.
person Ryan Townsend
works_on
Declarative Partial Updates concept
Plans to push browser vendors to adopt this as his first browser API.
role: advocate

Provenance

Read by
1 extraction