Intent to Prototype: Declarative fragments

123 views
Skip to first unread message

Chromestatus

unread,
Jul 16, 2026, 3:54:55 PM (11 hours ago) Jul 16
to blin...@chromium.org, nrose...@chromium.org
Contact emails
nrose...@chromium.org

Explainer
https://github.com/WICG/declarative-partial-updates/blob/main/fragment-include-explainer.md

Specification
No information provided

Summary
Declaratively control various aspect of HTML fragments: - Sanitize them - Bring them from a separate URL (aka "client side include") - Buffer them instead of stream

Blink component
Blink>HTML>Parser

Web Feature ID
Missing feature

Motivation
Composing different bits of HTML is one of the first things developer reach out for - but the platform doesn't provide it. Instead, people have to turn to bespoke and fragmented server-side solutions, or to bespoke and fragmented JS. With the added value of control flow (buffering vs. streaming) and sanitization, there is now more to be offered by enabling this kind of capability as a client-side feature.

Initial public proposal
https://github.com/whatwg/html/issues/2791

Goals for experimentation
None

Requires code in //chrome?
False

Tracking bug
https://issues.chromium.org/issues/535664974

Estimated milestones

No milestones specified



Link to entry on the Chrome Platform Status
https://chromestatus.com/feature/5188900898340864?gate=6299859587039232

This intent message was generated by Chrome Platform Status.
Reply all
Reply to author
Forward
0 new messages