Skip to content

PNG rasterizer captures the initial hidden motion frame instead of the required complete static frame #312

Description

@rudycelekli

Problem

The PNG procedure requires the deterministic complete static frame for motion-enabled diagrams, but its executable Rasterize snippet opens the ordinary source URL and never checks the frame. With the unchanged shipped policy-trace controller and ordinary step mode, the exact snippet successfully captures while the root still reports data-frame="start"; the explanatory steps remain hidden.

A local reproduction copies the shipped animated HTML and removes remote font links to isolate controller behavior. It runs the exact documented snippet with one read-only frame probe immediately before capture. The same native Chromium used by the repository gates reports frame_at_capture=start and writes a PNG. The reference and README already require ?motion=static, document.fonts.ready, and a data-frame="static" assertion.

Proposed scope

Make that existing static-export requirement executable in the PNG snippet: navigate with the static override, await font readiness, and refuse capture if a motion root fails to reach the complete static frame. Add native successful static capture and broken-controller/incorrect-frame controls while preserving ordinary static export and stalled-webfont fallback. No controller, example, template, or motion policy changes.

Codex is assisting @rudycelekli with reproduction and implementation.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions