Contact emails [email protected]
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. -- You received this message because you are subscribed to the Google Groups "blink-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/6a593703.5144260f.1484e7.0562.GAE%40google.com.
