Skip to content

Infrastructure: Qualify Windows/Win32 capture fidelity and provenance #4348

Open

Description

@JasonVMo

Current status - 2026-11-16

Capture qualification remains open and can proceed independently on authorized interactive endpoints.

Landed: #4463 immutable MCP PNG resource lifetime (artifact/reference behavior only, not recognizable content, pixel fidelity or crop/DPI correctness). #4498 (remote session, baseline 505a2187b) recorded Windows and Win32 clear/capture subcases: minimized capture refused without implicit restore, then explicit restore and a valid capture (Windows 586 × 793, Win32 1010 × 761). These are subcases at one DPI, not fidelity or crop qualification.

Not run (still unqualified): 200% DPI (changing the scaling setting was not authorized), mixed DPI and negative-origin layouts (one origin-zero monitor), 100%/150% window and element crops, overflow/focus rings, occlusion, lock/noninteractive/session-authority preflight, cancellation and cleanup against real captures.

Hosted Graphics Capture can be unavailable (0x80070057); capability-gated skips are not passes. Native --permissions doctor support is unavailable on Windows; no privacy/input setting may be changed implicitly. Preserve original artifacts and per-artifact provenance without exposing credentials, paths or raw native handles. Full interactive capture/environment subcases are tracked with #4441. The driver implementation plan records the Windows work and gates; per-run evidence lives in pull request descriptions and issue comments, and each package's references/current-status.md keeps only the latest result per native endpoint with a link.

Goal

Qualify native Windows Fabric/Win32 capture and add per-artifact provenance above the implementation delivered by #4260. Parent: #4275.

Status - 2026-10-01

Open; the capture backend is implemented. PR #4306 delivered window-scoped Windows Graphics Capture, D3D11 readback, WIC PNG encoding, element crops, scale factors, and explicit minimized/unavailable-capture errors.

Do not repeat the obsolete WinAppDriver-versus-desktop-fallback experiment: the supported driver is Appium-independent. Current documentation still requires interactive capture and live-DPI qualification; a native self-test or green semantic smoke job does not provide it.

Remaining scope and acceptance criteria

  • Capture representative Composition content on unlocked interactive Windows Fabric and Win32 Paper endpoints, with retained original PNGs and native bounds.
  • Qualify window and element crops at live 100%, 150%, and 200% DPI on both endpoints, including edges/focus rings/overflow, scale conversions, occlusion, and secondary windows.
  • Prove recognizable nonblank content and correct dimensions/crops; provider/transport success alone is not capture fidelity.
  • Record per-artifact backend/source, endpoint/renderer, window/element identity, logical bounds, pixel dimensions, scale/DPI, helper/manifest/runtime identities, and capture outcome. Do not expose raw native handles as the public identity.
  • Perform explicit locked/noninteractive/session-authority preflight and return distinct capture-unavailable diagnostics before attempting an invalid capture. Minimized windows remain unsupported unless a reviewed restore policy is added.
  • Measure the selected hosted/interactive runner's capture reliability and keep unqualified or unavailable coverage visible.
  • Verify artifact confinement, privacy/redaction, bounded output, failure behavior, and ownership-safe cleanup against real captures.
  • Update driver/Storybook reproduction and artifact documentation, with relevant automated checks and evidence links.
  • Screenshots remain optional visual evidence. Capture failures are explicit infrastructure/coverage results, and pixel differences never become a deterministic gate under this issue.

Evidence and coordination

Activity

  1. JasonVMo commented on Nov 16, 2026

    @JasonVMo
    ContributorAuthor

    Status update. #4498 recorded Windows and Win32 clear/capture subcases at baseline 505a2187b: minimized capture was refused without implicit restore, and after an explicit restore a valid capture was produced (Windows 586 × 793, Win32 1010 × 761). These are single-DPI subcases, not fidelity or crop qualification. Not run: 200% DPI, mixed DPI, negative-origin layouts, 100%/150% crops, occlusion and lock preflight. All acceptance criteria remain open. The broken #windows-and-win32-qualification link in the body now points at the driver plan's M6 section.

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

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions