Every surface at once
Nothing here fails on an old engine. Every missing capability costs a wire form, a fill mechanism, or an animation.
Chromium, Firefox and WebKit, never aggregated, with WebKit labelled a desktop proxy rather than an iOS number.
It says “not measured” with a reason instead of reporting a zero.
In plain terms
A browser engine on a laptop is not a phone. Three engines are measured directly; iOS and Android are real lanes that refuse to run until a device is attached, because a desktop proxy has nothing honest to fall back on.
The target is every surface at once: desktop browsers, mobile browsers, embedded webviews and old devices. Nothing in this design fails on an old engine — every missing capability costs a wire form, a fill mechanism, or an animation, and never the page.
| Surface | Engine | What it costs |
|---|---|---|
| Chrome, Edge, Electron | Chromium | Nothing. The Chromium-only bonuses are available. |
| Safari, iOS webviews | WebKit | No compression dictionaries and no speculation rules. |
| Firefox | Gecko | No cross-document view transitions in stable. |
| An old Android webview | An old Chromium | In-order streaming and full navigations, which is how the web worked. |
A degradation ladder, not a feature check
Every mechanism on this site has a rung below it that the browser already implements. Out-of-order fill needs a 330-byte inline script; without it the page streams in order. A delta needs a resident template; without one the region arrives as html. Navigation staging needs an epoch; without it a click is a navigation.
Which means the bottom rung of every ladder is a page that works with JavaScript switched off.
The device tier is a read, so it is an axis
A read with three values is an axis
examples/deviceLow cardinality is what lets a read become an ahead-of-time permutation rather than a branch taken per request.
This deployment thinks you are on a device, so the plan reachable from here is the one built for that tier.
app/fragments/examples/device.tsximport { fragment, type Ctx } from '@weftjs/core'
/**
* A read with three possible values, which is what makes it an ahead-of-time permutation.
*
* `ctx.device()` taints `device`, and the plan can carry a branch per value rather than a branch
* taken per request: low cardinality is the property that lets a read become an axis. The fragment
* does not know which one it will be rendered for, and does not need to.
*/
export default fragment(async (ctx: Ctx) => {
const tier = ctx.device()
return (
<p class="device">
This deployment thinks you are on a <strong>{tier}</strong> device, so the plan reachable from here is
the one built for that tier.
</p>
)
})
What the compiler knows
Holes
| Binding | Hole | Escape |
|---|---|---|
tier | text | escape |
What the client wires on adoption
No wiring: nothing on this template changes after it is painted, so the client attaches nothing to it.
- Sealed templates
- 1
- Version
63c7968954e0ae5445e34cdda1d5153e
The facts below show device in the read set. The plan can carry a branch per value; the fragment does not know which one it is rendered for.
Three values is low cardinality, and low cardinality is what lets a read become an ahead-of-time permutation instead of a branch taken per request. The plan can carry a branch per tier; the fragment never learns which one it was rendered for.