Level 1 only ships document.startViewTransition(): one transition at a time,
snapshotting the whole viewport. Level 2 adds
Element.startViewTransition(), so a transition can be scoped to a single
subtree, several of them can run concurrently, and
view-transition-name on nested elements is resolved per scope. This page
tracks the same feature across all three engines against the same WPT suite.
const transition = card.startViewTransition(() => updateCard());
await transition.finished;
main, shipped, no flag;
Firefox
90/93
bug 2075158, patches in prep;display-change-during-transition
css-view-transitions/scoped)
| Engine | Tracking | Scoped suite | Sampler | Updated (wpt sha) |
|---|---|---|---|---|
|
|
baseline chromium/src@main, no patches (shipped) |
90/93 | vt/chromium/ | 2026-11 · wpt e8ca14556268 |
Firefox
|
patch Bugzilla meta 2075158, Phabricator stack in preparation | 90/93 | firefox/i-2075158/ | 2026-11 · wpt e8ca14556268 |
WebKit
|
patch GitHub PR #81741 | 93/93 | webkit/i-pr81741/ | 2026-11 · wpt e8ca14556268 |
Same capture page in each engine: a scope that escapes its own clip but stays inside an
ancestor's overflow: hidden region, so the overlay flies out of the scope and
gets cut by the amber dashed box. Before = unpatched / pref off, after = with the patch.
Firefox source: nested-clip.html.
src@main, no flag toggledbaseline