← back to v150 · out-of-order-streaming
conformance · v150
v150 · out-of-order-streaming — conformance probe
6 assertions drawn from the spec. Each is a single contract the spec text makes. Pass/fail reflects what this browser executed; blocked means the contract was not run because it needs user mediation, hardware, or another unavailable precondition. Open the page in Chrome stable / canary / Firefox / Safari to compare.
0
pass
0
fail
0
blocked
6
total
| id | contract | kind | verdict | detail |
|---|---|---|---|---|
processing-instruction-node-type |
ProcessingInstruction nodes use nodeType 7, the DOM node type used for patching markers. spec ↗ | script | … | |
template-for-attribute-carrier |
<template for> can carry the target range name used by declarative patches. spec ↗ | script | … | |
live-route-serves-streamed-html |
The showcase live route serves a no-store text/html document containing processing-instruction ranges and template patches. spec ↗ | script | … | |
all-concepts-have-live-template-streams |
Every out-of-order streaming concept exposes a live streamed route with literal template-for patches. spec ↗ | script | … | |
native-streamed-patches-apply |
A streamed chunk-ordering document applies template patches natively, leaving patched content and no unapplied template-for elements. spec ↗ | script | … | |
repeated-marker-patches-append |
Repeated template patches that include a fresh marker append ordered AI token spans to the same range. spec ↗ | script | … |