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 81aff32
Browse filesBrowse the repository at this point in the historyBrowse files
fix(ios-runner): one synthesize-then-fallback helper; sequence taps use the standalone tap policy (callstack#2865)
* fix(ios-runner): route every synthesized gesture through one fallback helper
A synthesized tap step inside `sequence` resolved its context with the
synthesized-drag policy, so it refused the XCTest coordinate fallback when
accessibility was unavailable and failed outright when no window frame
resolved. A standalone synthesized tap falls back in both cases.
`performSynthesizedGesture` now performs the synthesized gesture, decides the
XCTest coordinate fallback from the gesture kind's policy, and logs the
decision. Selector tap, coordinate tap, sequence tap step, type focus and
drag use it; each site keeps its own XCTest gesture and bookkeeping. A
sequence tap step takes the coordinate-tap policy, and the fallback decision
reads the kind rather than a policy copy on the coordinate context.
Remove the unused `whenAccessibilityHealthy` keyboard policy, the drag
fallback branch that a nil frame could never reach, and the text-entry focus
predicate the helper replaces. Scroll keeps `privateSynthesisRequired`.
Fixescallstack#2788
* fix(ios-runner): route the in-app back tap through the synthesized gesture helper
Pin the sequence tap step fallback at the sequence command response with a
simulator test that forces private tap synthesis to fail while accessibility
is unavailable.
* docs(changelog): note the synthesized sequence tap fallback
0 commit comments