parser-backed streamed HTML

Chunk Ordering

This page loads a real Deno-streamed HTML document. The shell contains <?start name="hero">, <?start name="related">, and a result insertion range. Later response bytes contain literal <template for> patches.

stream evidence

normative pattern

<section>
  <?start name="hero">Loading hero...<?end>
</section>

<template for="related">...</template>
<template for="results">
  <li>Result 1</li>
  <?marker name="results">
</template>
<template for="hero">...</template>

what to inspect

The iframe route is a streamed text/html response, not a client-side simulation.
The byte log shows <template for="related"> and <template for="results"> arriving before the slow hero patch in the default scenario.
In browsers without native support, the streamed document keeps its fallback placeholders and shows an unsupported warning after the stream closes.

references

implementation reference

Need the exact API surface, compatibility boundaries, errors, lifecycle, and source links? Read the matching gendn reference ↗