Skip to content

v2: Full-page capture beyond the viewport #94

Description

@loyality7

Context

v1's screenshot only captures the visible viewport. Two candidate mechanisms exist and the choice needs a spike, same rigor as v1's protocol-backend spike:

  1. The process-global whole-document draw setting — must be applied before any view exists, so it becomes a library initialisation option, not a per-call flag.
  2. Scroll-and-stitch.

Scope

  • A spike measuring both approaches: correctness on a long/complex page, memory cost, and time cost.
  • Written GO/NO-GO per approach, then implement whichever wins.

Acceptance criteria

  • Spike produces measurements for both approaches on a real device
  • Written decision recorded before implementation starts (same discipline as the v1 protocol spike)
  • Chosen approach captures a page taller than the viewport correctly, verified against a fixture page built for this

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

    P2Wanted in v1, first to be cutarea:captureScreenshots, response bodies, tracing, HAR

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions