A clear direction.
A wider perspective.

Ready content, a stable header.

This example uses the current v38 controller. Serve both pages over HTTP(S) to try real same-origin document navigation. The header and hero background are immediately available on direct entry; only the title and description fade in over 350 ms.

Internal navigation retains the current content while preparing the destination, then uses a native 300 ms content crossfade where cross-document View Transitions are supported. The named header remains stable. Unsupported browsers use ordinary native navigation; reduced motion changes pages directly.

A genuine wait beyond 350 ms shows a compact nonmodal cube at the lower right. It loops every 2 seconds, including during longer waits. Ready content is never held for the drawing; the panel exits over 200 ms, with an immediate reset before a native transition snapshot. At 8 seconds it offers retry or stay controls. Offline and failure states use a static cube.

These two pages contain no artificial network delay. Use the separate simulated preview to inspect waiting, failure and retry cases.

Open the other example pageExplore simulated statesBack to cube specimen