Frame lifecycle

Everything, in order.

  1. 0.0s

    Signal acquired

    A single pointer event enters the pipeline and is stamped with a monotonic clock.

  2. 0.3s

    Intent resolved

    Gestures are classified against the last few frames of motion history.

  3. 0.9s

    State reconciled

    The optimistic update is merged and broadcast to every connected peer.

  4. 1.4s

    Layout committed

    Only the dirty region repaints; everything else stays on the compositor.

  5. 2.1s

    Motion settled

    Springs relax to rest and the frame budget is handed back to the browser.

  6. 2.8s

    Idle reached

    Work drains, listeners quiesce, and the surface waits for the next signal.