Skip to content

Commit b4ec027

Browse files
committed
docs(ios): name the probe-side owner and the screen-space dispatch basis (#3899)
Amends ADR 0004 to name ResolvedTextEntryInput as the probe-side owner of the content vector, cites the measured Add-button rect at (659,321), records that the runner republishes a windowed capture in screen space where the bridge-refusal warning said it was offset, and names screen space plus the app.frame origin assumption in the interactionCoordinate comment.
1 parent 009b65c commit b4ec027

2 files changed

Lines changed: 5 additions & 5 deletions

File tree

‎apple/runner/AgentDeviceRunner/AgentDeviceRunnerUITests/RunnerTests+TextEntryFocus.swift‎

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -185,7 +185,8 @@ extension RunnerTests {
185185
let readyTarget = TextEntryTarget(
186186
element: stabilized.element ?? target,
187187
refreshPoint: requestedPoint,
188-
prefersFocusedElement: false
188+
prefersFocusedElement: false,
189+
contentTranslation: contentTranslation
189190
)
190191
let element = stabilized.focusConfirmed
191192
? readyTarget.element

‎docs/adr/0004-ios-snapshot-backend-strategy.md‎

Lines changed: 3 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -768,10 +768,9 @@ If the frames differ, the guest refuses the capture (`app-window-not-full-screen
768768
This refusal provides evidence about the screen arrangement, not the app, so it has capture scope.
769769
If the runtime cannot report either frame, the guest keeps the capture.
770770

771-
The XCTest fallback is not correct for a windowed app either.
772-
The runner clips window-relative element frames against the screen-relative app frame.
773-
That is a runner gap.
774-
It is not a reason to publish a bridge tree that is known to be wrong.
771+
The XCTest fallback is the correct capture for a windowed app, after the amendment above.
772+
Before it, the runner clipped window-relative element frames against the screen-relative app frame, and that gap is what made this refusal protect a real failure.
773+
The refusal stays: this channel reports window-relative frames and no channel here converts them.
775774

776775
Rejected alternatives:
777776

0 commit comments

Comments
 (0)