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 e35d8de
Browse filesBrowse the repository at this point in the historyBrowse files
feat(gesture): add gesture tap with 2 to 5 simultaneous contacts (#3847)
* refactor(gesture): rename the two-contact plan topology to multi
Multi-contact guards now test topology !== 'single', so a later multi-contact intent reaches the same checks. No behaviour change.
* feat(gesture): add gesture tap with 2 to 5 simultaneous contacts
gesture tap touches 2 to 5 distinct points at once and lifts them together after --hold-ms (default 50 ms). --count and --pause-ms repeat the same contacts: each repetition plans against a fresh viewport, the series is budgeted against the request envelope, and an aborted request stops between repetitions. The CLI, .ad replay, Node.js client (tapGesture) and MCP accept it; gesture now refuses flags a kind does not read. Taps admit through the multi-touch tier; WebDriver maps them to its multi-pointer capability.
* feat(apple): accept multi-finger tap plans in the iOS runner
The runner admits a multi-topology tap with 2 to 5 stationary contacts on distinct points; pan, pinch, rotate and transform still need exactly two. The private XCTest bridge already synthesizes one path per contact, so it is unchanged.
* feat(android): inject multi-finger tap plans from the snapshot helper
The helper accepts a tap plan with 2 to 5 stationary contacts and generalizes its pointer schedule to N contacts: extra contacts go down in ascending index before the first sample and lift in descending order after the last, so the changing contact is always the highest active index. Transition spacing shrinks below 8 ms only when needed to fit every contact before the first sample; two-contact schedules are unchanged. Sample offsets are now checked for every path, not just the first two. A contracts test pins the 5-contact cap across TypeScript, Swift and Java.
* docs(gesture): document gesture tap and amend ADR 0013
GestureLab reports multi-tap rounds and the most contacts held in the last round, so a tap has an app-observed postcondition.
* fix(gesture): propagate cancellation without recording partial tap series
* refactor(gesture): keep cancellation checks at daemon boundaries
---------
Co-authored-by: Cameron Chisholm <[email protected]>
Copy file name to clipboardExpand all lines: android/snapshot-helper/src/test/java/com/callstack/agentdevice/snapshothelper/PointerEventScheduleTest.java
+47Lines changed: 47 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -25,6 +25,53 @@ static void run() {
25
25
"MOVE:2:2:32:true",
26
26
"POINTER_UP:2:2:32:true",
27
27
"UP:2:1:40:true");
28
+
// A short two-contact plan keeps its original schedule: the second contact goes down before
29
+
// the first move, and the last contact lifts 8 ms after the second.
0 commit comments