fix(docs): restore the code-block expand view transition

[mehdibha]

Summary

• fix(www): keep the page interactive during view transitions #438 set out to keep the page interactive during view transitions, but its second commit replaced the docs code-block expand/collapse morph with a height-only tween. The crossfade was gone: the new code appears at full opacity on the first frame and only the container height animates, which reads as an instant swap. This regression was noticed in the docs demos.
• Restore the scoped view transition from that PR's first commit: toggleCodeBlock names the figure for the transition's duration and runs flushSync(update) inside startViewTransition. The global fixes from fix(www): keep the page interactive during view transitions #438 stay in place (:root { view-transition-name: none } and ::view-transition { pointer-events: none } in styles.css), so only the block morphs and the rest of the page keeps its hit-testing.
• Reduced motion skips the transition (the global CSS also kills the pseudo animations).

Verification

Headless Chrome on /docs/components/button (InteractiveDemo, DynamicPre deferred highlighting) and /docs/components/text-field (Demo), expand and collapse, sampling every frame:

• The view-transition pseudo animations run for ~250ms and the block's transition name clears when they finish.
• document.elementFromPoint over a sidebar link returns the link on every frame of the transition, except the single snapshot frame.
• pnpm check and pnpm typecheck pass. No registry files touched.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
dotui	Ready	Preview	Sep 1, 2026 9:42pm UTC