Wisevoter
World

Web Standard Added Out-of-Order HTML Streaming

The latest HTML Living Standard enables declarative streaming to improve webpage loading performance.

Updated on Sept. 22, 2026 in Internet

Isometric editorial illustration of floating modular server blocks in teal and cream, representing structured digital data delivery.
The WHATWG HTML Living Standard now supports declarative out-of-order streaming, enabling browsers to prioritize loading visible page elements to enhance user-perceived performance. AI Illustration. Upload story photo >

Live Poll

Do you prefer browsers to load interactive page sections immediately instead of waiting for full completion?

The WHATWG HTML Living Standard has adopted declarative markup primitives for out-of-order streaming. This update allows browsers to render webpage sections as data arrives, preventing slow elements from blocking the entire load.

Why it matters

The proposal aims to solve long-standing performance bottlenecks where compute-heavy page parts delay the display of a full page. By allowing out-of-order streaming, developers can ensure that essential content reaches the user faster.

Browsers now support declarative streaming through new attributes that allow the parser to match identifiers and insert template contents into the DOM. Chrome and Edge version 151 further expand these capabilities with specific template element support.

The players

WHATWG

This is the community of developers who maintain and evolve the HTML Living Standard.

Google

Google develops the Chrome browser and contributes heavily to web standardization efforts.

Microsoft

Microsoft develops the Edge browser and participates in the evolution of open web standards.

Apple

Apple develops the WebKit engine that powers Safari and has officially supported this new standard.

Mozilla

Mozilla operates the Firefox browser and provides input on prospective changes to web specifications.

The details

The standard allows browsers to patch placeholders dynamically as data arrives via declarative HTML or matching JavaScript APIs. WebKit has published a positive position on the standard, while Mozilla has signaled receptive interest.

Timeline

  1. Facebook pioneered early BigPipe streaming techniques in 2009.

  2. Chrome and Edge version 150 introduced the initial declarative streaming support.

  3. Chrome and Edge version 151 added template element functionality.

  4. The official article reporting these changes was published on September 21, 2026.

The Tech Race

This HTML update marks a formal standardization of concepts similar to Facebook BigPipe streaming techniques. By moving these patterns into the browser spec, the industry is shifting away from proprietary hacks toward unified, performant infrastructure.

Users will notice faster page rendering times as websites adopt these new declarative standards. Developers can now implement complex page structures without needing to resort to custom, fragmented JavaScript solutions.

The takeaway

Standardized streaming enables a more efficient web where page content is painted as soon as it is ready. Developers should monitor the integration of these template features into their current rendering pipelines to optimize user experience.

Further reading

Explore the latest developments in web infrastructure on the Internet section page.

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?