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 a49fee9
Browse filesBrowse the repository at this point in the historyBrowse files
test(ios): the bridge test asks for what the AX server can give
XCTAutomationSupport declares HasNativeFocus and FocusedApplications and
no keyboard-focus attribute, so the mapper drops the hasKeyboardFocus
keypath and the private-AX fallback reports the focus engine's focus
alone; the XCTest producers carry keyboard focus. The test now asserts
the request names the native focus and that a snapshot arriving with
keyboard focus reads as focused, and the bridge comment says why the
keypath stays.
Copy file name to clipboardExpand all lines: apple/runner/AgentDeviceRunner/AgentDeviceRunnerUITests/UnitTests/RunnerTests+AXRecoveryConformanceTests.swift
+8-11Lines changed: 8 additions & 11 deletions
Original file line number
Diff line number
Diff line change
@@ -378,9 +378,10 @@ extension RunnerTests {
378
378
returnobservation
379
379
}
380
380
381
-
/// The bridge asks the AX server for `hasKeyboardFocus` beside `hasFocus` and reports either as
382
-
/// `focused`: the field a software keyboard is typing into holds keyboard focus only, and a
383
-
/// capture that read `hasFocus` alone left it unfocused.
381
+
/// The bridge reports keyboard focus as `focused` when the snapshot carries it, beside the focus
382
+
/// engine's focus it asks the AX server for. The server exposes no keyboard-focus attribute, so
383
+
/// the request names the native focus only; a snapshot that arrives with keyboard focus set (the
384
+
/// XCTest producers' case) still reads as focused through the shared OR.
0 commit comments