Disclose an unsettled post-gesture surface on selector-targeted interactions
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 3/5
- Tempo stimato
- 1-2 giorni
- Idoneità per principianti
- 65/100
- Tipo di issue
- Funzionalità
- Chiarezza
- Abbastanza chiara
- Stato di attività
- Attiva
- Stack tecnologico
- typescript
- Ambito
- mobile-dev, testing
Direzione di ricerca
Start by reading src/commands/interaction/runtime/resolution.ts around lines 733-752 where captureSnapshot is called. Understand how selector-targeted interactions like click and press resolve. Then examine src/daemon/deferred-interaction-outcome.ts to see how SnapshotState.unsettledGesture is set, and src/daemon/capture-disclosure.ts to see how selector reads disclose this fact. The goal is to modify the resolution logic to also disclose unsettledGesture when a target is missing from a tree with that fact, matching the behavior of selector reads.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
Problem
#2839 makes a post-gesture capture that never settled carry unsettledGesture, and discloses it on selector reads (is, get, find, wait) and snapshot. Selector-targeted interactions do not disclose it yet. click, press, fill, and similar commands resolve their target through src/commands/interaction/runtime/resolution.ts (the captureSnapshot call near lines 733-752). After a scroll whose surface is still moving, a target missing from that tree fails as a plain not-found. The agent cannot tell this apart from a real absence.
Expected
An interaction whose selector resolution misses on a tree with unsettledGesture carries the same typed unsettledGesture fact and warning as the selector reads. It must be keyed on the tree fact and must not match on message text.
Notes
- The fact is stamped on
SnapshotState.unsettledGesturebycapturePostGestureStabilizedResult(src/daemon/deferred-interaction-outcome.ts). - The selector reads disclose it through
withCaptureDisclosures(src/daemon/capture-disclosure.ts). - Follow-up to #2839.
- Lingua principale
- TypeScript
- Stelle
- 4.7k
- Fork
- 304
- Merge medio
- 11h 46m
- PR unite (30g)
- 496
Guida per i contributori
Apri la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di callstack/agent-device
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 75/100
callstack/agent-device#2842 ·
-
docs(ios-runner): RUNNER_PROTOCOL.md points at the wrong file and omits recovery and busy codes Apertadocumentation good first issue ready-for-agent
Difficoltà 2/5 1-3 ore Idoneità per principianti 75/100
callstack/agent-device#2797 ·
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
callstack/agent-device#1869 ·
-
Difficoltà 3/5 1-2 giorni Idoneità per principianti 55/100
callstack/agent-device#2856 ·
-
Difficoltà 4/5 3-5 giorni Idoneità per principianti 45/100
callstack/agent-device#2833 ·
Tutte le issue di callstack/agent-device
Issue simili
-
VerificationGate: ATTRIBUTION quote guard never matches a normal quotation (\b around the quote) Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 75/100
danielmiessler/LifeOS#2234 ·
-
T: Bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 75/100
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 65/100
-
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 85/100
-
Mend: dependency security vulnerability untriaged
Difficoltà 2/5 1-3 ore Idoneità per principianti 70/100