You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 5a24030
Browse filesBrowse the repository at this point in the historyBrowse files
fix(ios): derive hittable from geometric actionability on the AX bridge
The snapshot capability table has declared `hittable = geometric-actionability` for
every iOS backend (#1933), and the XCTest runner has always stamped it. When 0.21.0
made the host AX bridge the Simulator's snapshot source, the bridge reader mapped the
traits word into `enabled` and `selected` but handed over no hit result and disclosed
`hittability` as unavailable on every capture (#2638). A `hittable:` selector therefore
matched nothing on the bridge that the runner would match.
The reader now stamps `hittable` on its raw nodes from the node's own frame and the
reported viewport, using a shared `isGeometricallyActionable` that is the TypeScript twin
of the runner's Swift `SnapshotGeometry.isGeometricallyActionable`, `CGRect.contains`
half-open edges included. It discloses `hittability` as unavailable only when no viewport
is reported, keeping the residue owner the fact owner (#2199). Stamping the raw source
rather than the fold makes `snapshot --raw` match too.
This restores `hittable` parity between the two producers. It does not resolve the two
native-stack Maestro flows that motivated the investigation: those are a separate
behind-modal occlusion capture divergence, tracked apart.
Co-Authored-By: Apex <[email protected]>
0 commit comments