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 5f179ae
Browse filesBrowse the repository at this point in the historyBrowse files
fix(selectors): count only measurable fields and read password facts
A field with no usable bounds counted as on-screen, so it could take the
focus or turn a single field into an ambiguity before the touch point could
reject it. A password fact on an unrecognized type was ignored, so focus
went to the container instead.
Say in the help and docs that a named field wins over its neighbours and
that target_disabled is a reason, and record why the nested-field refusal
follows find's refusal contract for printed refs.
Refs callstack#3734
'Scroll in a direction, or toward the top/bottom edge of scrollable content. Set until to a selector to reach an off-screen target in one command rather than a scroll-and-check loop. The optional amount is the finger-path fraction of the viewport axis, honored up to 0.8 of it; directional scrolls reduce release momentum, while app scroll physics determine the final content offset. A visible keyboard shortens the swiped band instead of being dismissed; when too little is left, the command refuses with scroll_keyboard_occludes_surface. A directional scroll also reports the movement it observed as movement: moved, at-edge, unchanged, or unobserved when the two reads could not back a claim either way; an unchanged surface inside a container that still hides content in that direction refuses with scroll_no_progress rather than repeating the requested distance. The movement field is absent where a tier verifies per pass (top/bottom, until), where the runtime cannot read a screen, or where a settle observation or a replay already owns that observation.',
78
78
get: 'Read text or accessibility attributes from a snapshot ref or selector without changing the app. Use format text for visible content or attrs for the element attribute map.',
79
79
is: 'Check whether a selector satisfies a UI predicate such as visible, hidden, exists, absent, editable, selected, focused, or text. `absent` passes only when one readable, complete, settled, unscoped, full-depth accessibility capture has zero matches. Use wait when the condition may appear asynchronously.',
80
-
find: 'Find by text/label/value/role/id and run action; the action defaults to click. The role locator matches snapshot kind vocabulary (button, text, text-field, switch, ...); pre-reconciliation leaf spellings (statictext, edittext, textview) stay accepted on the nodes that carried them during a deprecation window. The focus and type actions aim at a text field: the match when it is one or sits inside one, or else the one enabled on-screen field inside it. Several such fields refuse with AMBIGUOUS_MATCH and the field candidates, and a disabled field refuses with target_disabled. Web text boxes are not recognized as text fields.',
80
+
find: 'Find by text/label/value/role/id and run action; the action defaults to click. The role locator matches snapshot kind vocabulary (button, text, text-field, switch, ...); pre-reconciliation leaf spellings (statictext, edittext, textview) stay accepted on the nodes that carried them during a deprecation window. The focus and type actions aim at a text field: the match or the field holding it, even beside other fields, or else the one enabled on-screen field inside the match. Several fields inside the match refuse with AMBIGUOUS_MATCH and the field candidates, and a disabled field refuses with reason target_disabled. Web text boxes are not recognized as text fields.',
81
81
gesture:
82
82
'Perform a structured pan, fling, swipe, pinch, rotate, transform, tap, or drag gesture. Select the gesture kind, then provide only the inputs that apply to that kind. A tap touches 2 to 5 points at once; repeat it with count and pauseMs.',
"gap: the promotion half does run — the `findAct` row declares `hittable-ancestor-below-root`, so the seam dispatches the promoted ancestor's touch point unless `resolveFocusTarget` keeps a text field the locator named (regression-proven in packages/daemon/src/execution/interaction/internal/__tests__/find.test.ts) — but the annotation half never does: the response is the focus runtime's point payload, so a match still reporting `hittable: false` after promotion is accepted silently, where press/click/fill answer with `targetHittable: false` plus a hint. Closing it needs the annotation composed at this seam, which is response-shape work the `responseIdentity` waiver below also records.",
592
+
"gap: the promotion half does run — the `findAct` row declares `hittable-ancestor-below-root`, so the seam dispatches the promoted ancestor's touch point unless `resolveFocusTarget` chooses a text field instead (regression-proven in packages/daemon/src/execution/interaction/internal/__tests__/find.test.ts) — but the annotation half never does: the response is the focus runtime's point payload, so a match still reporting `hittable: false` after promotion is accepted silently, where press/click/fill answer with `targetHittable: false` plus a hint. Closing it needs the annotation composed at this seam, which is response-shape work the `responseIdentity` waiver below also records.",
593
593
trackingIssue: FIND_FOCUS_DISPATCH_GAPS_ISSUE,
594
594
},
595
595
// One construction site per dispatch kind, both shared with the plain commands: the focus
- Use `find ... wait <timeoutMs>` to wait for an element to appear.
56
56
- Pair `find` with a scoped snapshot (`snapshot -s "<label>"`) for speed.
57
-
-[Android] If the matched node is not hittable, agent-device clicks or focuses the nearest hittable ancestor.`find ... focus` and `find ... type` keep a matched text field as their target instead.
58
-
-`find ... focus` and `find ... type` aim at a text field: the match when it is one or sits inside one, or else the one enabled on-screen field inside it. Several such fields refuse with `AMBIGUOUS_MATCH` and the field candidates, and a disabled field refuses with `target_disabled`. Web text boxes are not recognized as text fields, so a web match keeps its own aim.
57
+
-[Android] If the matched node is not hittable, agent-device clicks or focuses the nearest hittable ancestor.
58
+
-`find ... focus` and `find ... type` aim at a text field: the match or the field holding it, even when it is not hittable or sits beside other fields, or else the one enabled on-screen field inside the match. Several fields inside the match refuse with `AMBIGUOUS_MATCH` and the field candidates, and a disabled field refuses with`COMMAND_FAILED` and reason`target_disabled`. Web text boxes are not recognized as text fields, so a web match keeps its own aim.
59
59
- Use `fill` to find a field and replace its text in one step. To append to the text in the focused field, use `click` or `press`, then `type`.
0 commit comments