HTML Standard Added Declarative Streaming
The WHATWG has formalized out-of-order HTML streaming, allowing browsers to render pages without waiting for slow components.
Updated on Sept. 22, 2026 in Internet
Live Poll
Do you prefer browsers to load interactive page sections immediately instead of waiting for full completion?
The WHATWG HTML Living Standard now includes native declarative primitives for out-of-order streaming. Chrome 150 and Edge 150 have implemented the initial features, with further template support arriving in version 151.
Why it matters
This update standardizes a technique pioneered by Facebook's BigPipe in 2009, enabling faster page delivery by ensuring slow-to-compute components no longer block the entire document load. The move reduces reliance on custom JavaScript-heavy implementations to manage asynchronous content delivery.
Browsers now support declarative markup that patches placeholders as data arrives, with version 151 adding specific template element integration. This replaces older, proprietary approaches to out-of-order content rendering.
The players
WHATWG
The Web Hypertext Application Technology Working Group is a community of vendors that maintains the HTML Living Standard.
Chrome
Google's web browser built on the Chromium engine that serves as a primary driver for web platform evolution.
Edge
Microsoft's browser built on Chromium that mirrors the core feature implementation timeline of Chrome.
WebKit
The browser engine developed primarily by Apple that powers Safari and has signaled a positive position on the standard.
The details
The new standard uses identifiers to match incoming data fragments with placeholders in the Document Object Model (DOM) — the programming interface for HTML documents. The browser parser processes these markers, removes them, and dynamically inserts the template contents into the page as they arrive via declarative HTML or JavaScript APIs. This allows complex, high-latency page sections to render independently of the main document stream.
Timeline
2009: Facebook pioneered the original BigPipe streaming techniques.
September 21, 2026: The standards development was confirmed.
The Tech Race
This standard updates the web architecture to natively support the performance patterns established by Facebook's 2009 BigPipe techniques. It represents a shift from proprietary framework-level implementations to a unified, browser-native approach for asynchronous page loading.
Web developers can now utilize these declarative attributes in Chrome 150 and Edge 150 to improve perceived load times without custom JavaScript. Users will experience faster content rendering for complex pages as support propagates across the browser ecosystem.
The takeaway
The move to standardize streaming effectively brings long-standing performance optimization techniques into the core web platform. Developers should monitor the integration of these features in WebKit and Mozilla Firefox to confirm broad cross-browser compatibility for their production environments.
Further reading
Explore deeper architectural shifts at Internet.
Source note: This article includes information reported by InfoQ.
Live Poll
Do you prefer browsers to load interactive page sections immediately instead of waiting for full completion?
