Base and head capture run in parallel, each on its own simulator, but the
fixture's fake agent-device kept one route, appearance and current session for
all of them. A head screenshot could take the base session's build, so /home
matched its base and the round-trip test intermittently listed five changed
screens instead of six. Each request names its session in the daemon URL; the
fake device now answers from that session's state.
- The PR comment counts screens whose captures were verified but that got no
verdict (the comparison did not run or failed) as "N not compared" with a
yellow result, and says "No compared screen changed" rather than claiming
nothing changed. Screens never captured stay unlisted.
- A screen accessibility-only on one platform and visibly changed on another is
listed and saved as the visible change, whichever platform comes first.
- The Viewer's Changes filter has an Accessibility only chip apart from
Modified, Compare reviews those screens after the visible changes, and the
focus survives in the URL.
- The agent API reports a failed or misattributed capture as unavailable, as
the Viewer does, and its index sentence names every status so the parts add
up to the total.
- A route family is accessibility-only only when every changed member is.
- Report summaries count changes as the comment lists them, map card handles
take the accessibility-only colour, and the local text names the status.
A screen whose source changed but whose screenshots were not compared was
listed as Source-affected: a guess from the code, not something the captures
showed. Explore reports what the captures show, so it is no longer a change.
The PR comment does not list or count it, the agent API reports it as
not-compared rather than modified, saved runs and the reports picker leave it
out, and the Viewer marks it Not compared and drops it from the legend. A
planned capture that failed is still counted as unavailable and named under
Validation.
A modified screen whose screenshots match changed only in what assistive
technology reads: its accessibility tree (a label, a role, an element added to
the tree). It was counted as a plain change in the PR comment, and the Viewer
called it "Changed (not visible)" and left it out of Compare and the Changed
filter. Screen readers and voice control see these changes, so they are now
named and reviewed as their own kind of change:
- The PR comment counts them apart ("3 visual changes · 12 accessibility
only") and lists them under 🟦 Accessibility only.
- The Viewer marks them "Accessibility only" in blue, with square marks so the
status does not rest on colour alone. Compare steps through them and Screens'
Changed filter keeps them.
- What changed lists what assistive technology reads under its own heading:
every finding on an accessibility-only screen, and label and role findings on
a screen whose pixels also changed. Highlight says there is nothing to
outline.
- The agent API reports status "accessibility-only" (sourceStatus "modified")
and includes it in the changed-screens link. The reports picker counts it.
The report contract is unchanged: the review status stays "modified" and
readers derive the label from the matching screenshots, so earlier reports read
the same way.
"description":"Source-driven mobile app maps, deterministic CI capture, and visual reviews",
"license":"MIT",
"type":"module",
Reference in new issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.