Feature Library

Mechanical panel choreography

<0.01 CPU ms
A still of the Mechanical panel choreography demo
Still
The live demo starts when it’s in view.Switch screens with the tabs or 1 2 3 · switch again mid-change to turn it round

On a screen change the old panels unbolt, unlatch and leave, and the new ones slide or swing in on their rails, hit a hard stop, ring back, latch and bolt…

What it costs a frame

<0.01 ms
GPU
not used
CPU, median
<0.01 ms
CPU, 95th pct
<0.01 ms
Draw calls
0
Weight
Light

Measured 13 November 2026 on RTX 4060 Laptop, 13th Gen Intel(R) Core(TM) i9-13900H, Chrome 157, 1920×1080 at 1×. 600 frames × 3 rounds, median kept (rounds ranged CPU <0.01–<0.01 ms). What ran: Measured changing screens by itself every 1.6 s, and every third change turned round halfway, so the frames hold the panels travelling, stopping, latching and bolting (and unbolting and leaving), with the latches and bolts drawn and the stage jolting on each stop. At rest the frame loop stops. Phones: tiers are being measured next.

On every machine it was measured on
MachineGPU msCPU msCPU p95
RTX 4060 Laptop · 13th Gen Intel(R) Core(TM) i9-13900Hreference · measuring toolnot timed<0.01<0.01
apple · Apple A19 Proin a browser tab · 16 November 2026not timed<0.010.02
Intel Arc 140V (Xe2-LPG) · Intel Core Ultra 7 258Vin a browser tab · 15 November 2026not timed<0.010.01

Bars against one 16.7 ms frame. A browser-tab run is timed in a visible tab without the tool’s scripted input, so read it as close, not exact.

What it needs

Renders with
DOM and CSSPlain DOM and CSS: every current browser.
Your browser
Runs hereNo WebGPU needed
Depends on
NothingNo other packages

What it’s for

  1. Switching the screens of a dashboard or a game menu
  2. Tabs that rebuild a whole view
  3. Mechanical, industrial or sci-fi looks
  4. Onboarding steps
  5. A kiosk or control-room interface

Pitfalls, in brief

  1. The screens must share one place: the module makes the stage a grid and puts every screen in its one cell.
  2. Panels are measured with their transforms off when a change starts and when the stage resizes.
  3. The module writes each panel’s transform.
  4. Hinged panels need backface-visibility (the module’s CSS sets it) and nothing on an ancestor that flattens 3D (overflow on the panel itself is fine; filter or opacity below 1 on the screen flattens it).
  5. Input never waits: the screen being left is inert at once and the new one is live at once, mid-travel.
3 more in brief
  1. Announce the change yourself (a polite live region, as the demo does).
  2. Reduced motion swaps the travel for a fade at the seat; latches and bolts are shown closed at once.
  3. stagger, the rig timings and decor are read when the choreography is made; timeScale can change live.
8 pitfalls in full, the hook-up guide, the module source and its tests come with the part.

Where it comes from

From HaTac. Fully custom code.

screen transitionschoreographystaggerinterruptiblereversiblehard stoplatchboltshingetabsreduced motioninertdomno dependencies

Near it in the frame