Skip to content

Commit b46ac6d

Browse files
thymikeeclaude
andcommitted
fix(ios): classify the keyboard dismiss refusal by what it dispatched
`keyboard dismiss` refused two different things with one untyped message, so a caller had to match prose to tell them apart. A keyboard that exposes no dismiss key and a dismiss control that was tapped and left the keys up are different verdicts: the first sent nothing, the second dispatched. The runner now answers the no-dismiss-key refusal with its own wire code, KEYBOARD_DISMISS_UNAVAILABLE, declared in RunnerWireErrorCode and classified by the existing runner-code table. It keeps the code the command already refused with, UNSUPPORTED_OPERATION, through a wireCode row, so the published code contract is unchanged, and it gains details.reason keyboard_dismiss_unavailable with dispatched: no. dismissKeyboard answers a RunnerKeyboardDismissOutcome carrying dismissControlFound, which also decides which of the two verdicts a tvOS keyboard stayed up for. Help, the runner protocol, and the command docs state which refusal sends nothing. Co-Authored-By: Claude Opus 5.5 <[email protected]>
1 parent ddbfc85 commit b46ac6d

14 files changed

Lines changed: 225 additions & 44 deletions

File tree

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

Lines changed: 2 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -587,23 +587,15 @@ extension RunnerTests {
587587
}
588588
return Response(ok: true, data: DataPayload(message: command.command.rawValue))
589589
case .keyboardDismiss:
590-
var dismissal: (wasVisible: Bool, dismissed: Bool, visible: Bool, mechanism: RunnerKeyboardDismissMechanism?)?
590+
var dismissal: RunnerKeyboardDismissOutcome?
591591
withBoundedInteractionIdleTimeoutIfSupported(activeApp, waits: .bothSkipped) {
592592
dismissal = dismissKeyboard(app: activeApp)
593593
}
594594
guard let result = dismissal else {
595595
return Response(ok: false, error: ErrorPayload(message: "keyboardDismiss produced no result"))
596596
}
597597
if result.wasVisible && !result.dismissed {
598-
return Response(
599-
ok: false,
600-
error: ErrorPayload(
601-
code: "UNSUPPORTED_OPERATION",
602-
message: "Unable to dismiss the iOS keyboard: the keyboard exposes no dismiss key, and background taps are never attempted (no tap outside the keyboard can be proven side-effect-free)",
603-
hint:
604-
"An element whose center sits behind the on-screen keyboard is refused with tap_keyboard_occludes_target; one whose center stays above the keys presses normally. To end editing, tap the app's own Done/Cancel control, or use keyboard enter to press the return key when submission is wanted."
605-
)
606-
)
598+
return Response(ok: false, error: keyboardDismissRefusal(dismissControlFound: result.dismissControlFound))
607599
}
608600
return Response(
609601
ok: true,

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

Lines changed: 70 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -31,6 +31,18 @@ enum RunnerKeyboardDismissMechanism: String {
3131
case dismissKey
3232
}
3333

34+
/// One `keyboard dismiss` attempt, plus the fact that decides how a refusal is classified:
35+
/// `dismissControlFound` says whether the runner ever dispatched a dismissal.
36+
struct RunnerKeyboardDismissOutcome {
37+
let wasVisible: Bool
38+
let dismissed: Bool
39+
let visible: Bool
40+
let mechanism: RunnerKeyboardDismissMechanism?
41+
/// Whether a dismissal was dispatched — the keyboard's own control was tapped, or the tvOS remote's
42+
/// Menu press landed. Only its absence proves the command sent nothing.
43+
let dismissControlFound: Bool
44+
}
45+
3446
/// Keyboard coverage read from the capture's complete pre-projection root snapshot on iOS XCTest.
3547
/// Visible frames include the input assistant and share the nodes' normalized coordinate space.
3648
/// A complete scan with no keyboard establishes absence; projected or partial trees never do.
@@ -189,20 +201,32 @@ extension RunnerTests {
189201
return visibleKeyboardFrame(app: app) != nil
190202
}
191203

192-
func dismissKeyboard(
193-
app: XCUIApplication
194-
) -> (wasVisible: Bool, dismissed: Bool, visible: Bool, mechanism: RunnerKeyboardDismissMechanism?) {
204+
func dismissKeyboard(app: XCUIApplication) -> RunnerKeyboardDismissOutcome {
195205
let keyboard = app.keyboards.firstMatch
196206
let wasVisible = isKeyboardVisible(app: app)
197207
guard wasVisible else {
198-
return (wasVisible: false, dismissed: false, visible: false, mechanism: nil)
208+
return RunnerKeyboardDismissOutcome(
209+
wasVisible: false,
210+
dismissed: false,
211+
visible: false,
212+
mechanism: nil,
213+
dismissControlFound: false
214+
)
199215
}
200216

201217
#if os(tvOS)
202-
_ = pressTvRemote(.menu)
218+
let pressedMenu = pressTvRemote(.menu)
203219
sleepFor(0.2)
204-
let visible = isKeyboardVisible(app: app)
205-
return (wasVisible: true, dismissed: !visible, visible: visible, mechanism: visible ? nil : .dismissKey)
220+
let tvVisible = isKeyboardVisible(app: app)
221+
return RunnerKeyboardDismissOutcome(
222+
wasVisible: true,
223+
dismissed: !tvVisible,
224+
visible: tvVisible,
225+
mechanism: tvVisible ? nil : .dismissKey,
226+
// `pressTvRemote` answers false only on a build that has no remote to press, so on tvOS the
227+
// Menu press went out and the refusal that follows did dispatch: it keeps the generic code.
228+
dismissControlFound: pressedMenu
229+
)
206230
#else
207231
if tapKeyboardDismissControl(app: app) {
208232
_ = keyboard.waitForNonExistence(timeout: KeyboardDismissObservationTiming.timeout)
@@ -213,7 +237,13 @@ extension RunnerTests {
213237
requiredConsecutiveMatches: KeyboardDismissObservationTiming.settleRequiredConsecutiveMatches
214238
)
215239
let visible = isKeyboardVisible(app: app)
216-
return (wasVisible: true, dismissed: !visible, visible: visible, mechanism: visible ? nil : .dismissKey)
240+
return RunnerKeyboardDismissOutcome(
241+
wasVisible: true,
242+
dismissed: !visible,
243+
visible: visible,
244+
mechanism: visible ? nil : .dismissKey,
245+
dismissControlFound: true
246+
)
217247
}
218248

219249
// #1606 review P1 (twice): generic background-tap dismissal is
@@ -222,10 +252,41 @@ extension RunnerTests {
222252
// indistinguishable from an inert backdrop, so a "safe-area" tap can
223253
// navigate or submit while reporting a successful dismiss. The dismiss
224254
// key is the only mechanism the runner can vouch for.
225-
return (wasVisible: true, dismissed: false, visible: isKeyboardVisible(app: app), mechanism: nil)
255+
return RunnerKeyboardDismissOutcome(
256+
wasVisible: true,
257+
dismissed: false,
258+
visible: isKeyboardVisible(app: app),
259+
mechanism: nil,
260+
dismissControlFound: false
261+
)
226262
#endif
227263
}
228264

265+
/// The refusal a visible keyboard that stayed up answers with. The two ways it stays up answer
266+
/// different questions and must not share one classification: finding no dismiss control sent
267+
/// nothing and is the runner's own typed refusal (`KEYBOARD_DISMISS_UNAVAILABLE`, so the host
268+
/// publishes its `details.reason` instead of leaving callers to read the prose), while a control
269+
/// that was tapped and left the keys up did dispatch and keeps the generic code.
270+
func keyboardDismissRefusal(dismissControlFound: Bool) -> ErrorPayload {
271+
if dismissControlFound {
272+
return ErrorPayload(
273+
code: "UNSUPPORTED_OPERATION",
274+
message: "Unable to dismiss the keyboard: a dismiss mechanism ran and the keyboard stayed visible",
275+
hint: keyboardDismissRefusalHint
276+
)
277+
}
278+
return ErrorPayload(
279+
code: RunnerWireErrorCode.keyboardDismissUnavailable,
280+
message: "Unable to dismiss the keyboard: it exposes no dismiss key, and background taps are never attempted (no tap outside the keyboard can be proven side-effect-free)",
281+
hint: keyboardDismissRefusalHint
282+
)
283+
}
284+
285+
private var keyboardDismissRefusalHint: String {
286+
return
287+
"An element whose center sits behind the on-screen keyboard is refused with tap_keyboard_occludes_target; one whose center stays above the keys presses normally. To end editing, tap the app's own Done/Cancel control, or use keyboard enter to press the return key when submission is wanted."
288+
}
289+
229290

230291
// AX-free on purpose (screenshot bytes, not the accessibility tree) so it holds
231292
// under the same AX degradation the synthesized gesture lane is built to survive.

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

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -58,6 +58,10 @@ final class RunnerTests: XCTestCase {
5858
static let backSwipeNoChange = "BACK_SWIPE_NO_CHANGE"
5959
static let backSwipeUnverified = "BACK_SWIPE_UNVERIFIED"
6060
static let backSwipeNotDispatched = "BACK_SWIPE_NOT_DISPATCHED"
61+
/// A `keyboard dismiss` the visible keyboard would not come down for: it exposes no dismiss key the
62+
/// runner vouches for (#1606). The host reports it under `UNSUPPORTED_OPERATION` and publishes
63+
/// `details.reason`, so a caller never reads the refusal off the message prose.
64+
static let keyboardDismissUnavailable = "KEYBOARD_DISMISS_UNAVAILABLE"
6165
/// Refuses a repeat of a `commandId` the runner already finished, when that command's own
6266
/// classification keeps no response body to replay. Nothing ran for the repeat, but the daemon's
6367
/// dispatch disclosure stays `unknown` — only the runner knows whether an earlier send of that id

‎apple/runner/AgentDeviceRunner/AgentDeviceRunnerUITests/UnitTests/RunnerTests+KeyboardTests.swift‎

Lines changed: 15 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -139,6 +139,21 @@ extension RunnerTests {
139139

140140
#endif
141141

142+
/// The two ways a visible keyboard stays up answer different questions, so they must not share one
143+
/// code (#1606). Finding no dismiss control sent nothing and is the runner's own refusal; a control
144+
/// that was tapped and left the keys up did dispatch and keeps the generic code. The host reads the
145+
/// first code's literal to publish `details.reason`, so it is pinned here as the wire value.
146+
func testKeyboardDismissRefusalNamesItsOwnCodeOnlyWhenNothingWasDispatched() {
147+
let notDispatched = keyboardDismissRefusal(dismissControlFound: false)
148+
XCTAssertEqual(notDispatched.code, "KEYBOARD_DISMISS_UNAVAILABLE")
149+
XCTAssertNotNil(notDispatched.hint)
150+
151+
let dispatched = keyboardDismissRefusal(dismissControlFound: true)
152+
XCTAssertEqual(dispatched.code, "UNSUPPORTED_OPERATION")
153+
XCTAssertNotNil(dispatched.hint)
154+
XCTAssertNotEqual(dispatched.code, notDispatched.code)
155+
}
156+
142157
func testKeyboardBandFactPublishesAbsenceWhenTheCompleteCaptureHasNoKeyboard() {
143158
let fact = runnerKeyboardBandFact(exists: false, frame: .zero)
144159
XCTAssertEqual(fact, .absent)

‎apple/runner/RUNNER_PROTOCOL.md‎

Lines changed: 13 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -252,12 +252,19 @@ Successful and failed responses use the same top-level envelope:
252252
{
253253
"ok": false,
254254
"error": {
255-
"code": "UNSUPPORTED_OPERATION",
256-
"message": "Unable to dismiss the iOS keyboard: the keyboard exposes no dismiss key (background taps are never attempted)"
255+
"code": "KEYBOARD_DISMISS_UNAVAILABLE",
256+
"message": "Unable to dismiss the keyboard: it exposes no dismiss key, and background taps are never attempted (no tap outside the keyboard can be proven side-effect-free)"
257257
}
258258
}
259259
```
260260

261+
The example is a `keyboard dismiss` the keyboard would not come down for; a refusal that can name a
262+
next step also carries `hint`, omitted here. A keyboard that stayed up answers one of two codes:
263+
`KEYBOARD_DISMISS_UNAVAILABLE` when it found no dismiss control and so sent nothing, or
264+
`UNSUPPORTED_OPERATION` when a dismiss control was tapped, or the tvOS remote's Menu press was sent,
265+
and the keyboard stayed visible. The host reports both under `UNSUPPORTED_OPERATION` and publishes the
266+
first one's `details.reason`.
267+
261268
`data` is command-specific. Common fields include snapshot nodes, text lookup results, gesture timing, visibility metadata, and screenshot or recording output details.
262269

263270
Capture-plan snapshots carry `snapshotViewport`, the acquisition's declared viewport evidence.
@@ -310,7 +317,9 @@ declaration for the current rules.
310317
the main-thread watchdog in [`RunnerTests+Transport.swift`](AgentDeviceRunner/AgentDeviceRunnerUITests/RunnerTests+Transport.swift). The daemon
311318
classifies a runner-reported code in `classifyRunnerReportedError`
312319
([`runner-contract.ts`](../../packages/apple-runner/src/runner-contract.ts)): codes listed in `DIAGNOSTIC_ONLY_RUNNER_ERROR_CODES`
313-
arrive as `COMMAND_FAILED` with `details.runnerErrorCode`, and other codes pass through as typed
314-
codes. How the daemon reacts to a failure (retry, resend, session-fatal) is declared in
320+
arrive as `COMMAND_FAILED` with `details.runnerErrorCode`, unless their row names the wire code the
321+
caller already reads that family under. Other codes pass through as typed codes. A code with a
322+
`RUNNER_REPORTED_ERROR_REASONS` row also publishes `details.reason`, so a caller never reads the
323+
refusal off `message`. How the daemon reacts to a failure (retry, resend, session-fatal) is declared in
315324
`RUNNER_ERROR_RULES` and the helpers beside it
316325
([`runner-error-classification.ts`](../../packages/apple-runner/src/runner-error-classification.ts)).

‎contracts/fixtures/dispatch-disclosure.json‎

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -301,6 +301,12 @@
301301
"trigger": "structured runner reply with code COMMAND_ALREADY_FINISHED: the journal refused a repeat of a spent commandId and kept no outcome to replay, so it cannot say what that command did",
302302
"dispatched": "unknown"
303303
},
304+
{
305+
"id": "ios-runner.reply.KEYBOARD_DISMISS_UNAVAILABLE",
306+
"producer": "ios-runner",
307+
"trigger": "structured runner reply with code KEYBOARD_DISMISS_UNAVAILABLE: `keyboard dismiss` refused because the visible keyboard exposes no dismiss key, before any tap",
308+
"dispatched": "no"
309+
},
304310
{
305311
"id": "ios-runner.reply.unlisted-code",
306312
"producer": "ios-runner",

‎packages/apple-runner/src/__tests__/index-dispatch-disclosure.test.ts‎

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -192,6 +192,8 @@ const DRIVERS: Record<string, () => Promise<unknown>> = {
192192
replyFailure('SYNTHESIZED_GESTURE_NOT_DISPATCHED'),
193193
'ios-runner.reply.SYNTHESIZED_GESTURE_OUTCOME_UNKNOWN': () =>
194194
replyFailure('SYNTHESIZED_GESTURE_OUTCOME_UNKNOWN'),
195+
'ios-runner.reply.KEYBOARD_DISMISS_UNAVAILABLE': () =>
196+
replyFailure('KEYBOARD_DISMISS_UNAVAILABLE'),
195197
'ios-runner.reply.unlisted-code': () => replyFailure('XCTEST_RECORDED_FAILURE'),
196198
'ios-runner.series.later-chunk-refused': pressSeriesRefusedOnSecondChunk,
197199
'ios-runner.series.invalid-step-before-send': pressSeriesWithInvalidStep,

‎packages/apple-runner/src/__tests__/runner-error-classification.test.ts‎

Lines changed: 50 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,6 +3,7 @@ import { test } from 'vitest';
33
import { AppError, createRequestCanceledError } from '@agent-device/kernel/errors';
44
import {
55
COMMAND_ALREADY_FINISHED_RUNNER_CODE,
6+
KEYBOARD_DISMISS_UNAVAILABLE_RUNNER_CODE,
67
MAIN_THREAD_TIMEOUT_RUNNER_CODE,
78
NO_TEXT_INPUT_AT_POINT_RUNNER_CODE,
89
RUNNER_SCREEN_CAPTURE_REFUSAL_RUNNER_CODES,
@@ -22,7 +23,10 @@ import {
2223
shouldRetryRunnerConnectError,
2324
} from '../runner-error-classification.ts';
2425
import { runnerConnectFailure, unwrittenConnectRefusal } from './runner-session-fixtures.ts';
25-
import { requireSwiftThrownErrorWireCode } from './runner-swift-settlement-fixtures.ts';
26+
import {
27+
requireSwiftKeyboardDismissRefusalWireCode,
28+
requireSwiftThrownErrorWireCode,
29+
} from './runner-swift-settlement-fixtures.ts';
2630

2731
const TAP = { command: 'tap' } as const;
2832
const SNAPSHOT = { command: 'snapshot' } as const;
@@ -169,6 +173,42 @@ test('a back swipe that proved nothing stays COMMAND_FAILED, unknown, with its o
169173
assert.equal(notDispatched.details.dispatched, 'no');
170174
});
171175

176+
// The keyboard stays up two different ways, and only one of them sent nothing. The literal is what the
177+
// Swift runner encodes, so it is the contract and not the constant name: a rename on one side has to
178+
// fail here rather than silently split the pair.
179+
test('a keyboard dismiss refused for having no dismiss key keeps its code and publishes its reason', () => {
180+
assert.equal(KEYBOARD_DISMISS_UNAVAILABLE_RUNNER_CODE, 'KEYBOARD_DISMISS_UNAVAILABLE');
181+
const refusal = classifyRunnerReportedError(KEYBOARD_DISMISS_UNAVAILABLE_RUNNER_CODE);
182+
// The code contract for `keyboard dismiss` is unchanged: the refusal travels under the code that
183+
// command already refused with, so a caller keyed on the code sees what it saw before.
184+
assert.equal(refusal.code, 'UNSUPPORTED_OPERATION');
185+
assert.equal(refusal.details.runnerErrorCode, 'KEYBOARD_DISMISS_UNAVAILABLE');
186+
assert.equal(refusal.details.reason, 'keyboard_dismiss_unavailable');
187+
assert.equal(refusal.details.dispatched, 'no');
188+
assert.equal(refusal.details.retriable, undefined);
189+
// The whole published shape: the runner's own code survives, the wire code it hides under does not.
190+
assert.deepEqual(refusal.details, {
191+
runnerErrorCode: 'KEYBOARD_DISMISS_UNAVAILABLE',
192+
reason: 'keyboard_dismiss_unavailable',
193+
dispatched: 'no',
194+
});
195+
const refusalError = new AppError(refusal.code, refusal.details.reason ?? '', refusal.details);
196+
assert.equal(isRetryableRunnerError(refusalError), false);
197+
assert.equal(isRunnerBusyError(refusalError), false);
198+
// The closest negative: the same refusal in prose alone, from an unclassified reply, earns no
199+
// reason, so a consumer keyed on `reason` cannot mistake it for the pre-dispatch refusal.
200+
const untyped = commandFailed(
201+
'Unable to dismiss the keyboard: it exposes no dismiss key, and background taps are never attempted',
202+
);
203+
assert.equal(untyped.details?.reason, undefined);
204+
// A dismiss control that was tapped and left the keys up did dispatch, so it keeps the generic code
205+
// and says nothing about dispatch.
206+
const dispatched = classifyRunnerReportedError('UNSUPPORTED_OPERATION');
207+
assert.equal(dispatched.code, 'UNSUPPORTED_OPERATION');
208+
assert.equal(dispatched.details.reason, undefined);
209+
assert.equal(dispatched.details.dispatched, 'unknown');
210+
});
211+
172212
test('retryable requires an AppError with COMMAND_FAILED', () => {
173213
assert.equal(isRetryableRunnerError(new Error('fetch failed')), false);
174214
assert.equal(isRetryableRunnerError(new AppError('DEVICE_NOT_FOUND', 'fetch failed')), false);
@@ -560,6 +600,15 @@ test('the runner declares the wire codes the daemon reads for occupancy', () =>
560600
);
561601
});
562602

603+
test('the runner declares the wire code the keyboard-dismiss refusal publishes its reason under', () => {
604+
assert.equal(
605+
requireSwiftKeyboardDismissRefusalWireCode(),
606+
KEYBOARD_DISMISS_UNAVAILABLE_RUNNER_CODE,
607+
'the runner must encode its no-dismiss-key refusal under the code the daemon maps to ' +
608+
'details.reason, or that reason becomes unreachable',
609+
);
610+
});
611+
563612
// --- runner that predates the listener token ---
564613

565614
test('a runner that does not require the token is session-fatal and never retried or replayed', () => {

‎packages/apple-runner/src/__tests__/runner-session-response.test.ts‎

Lines changed: 12 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -10,13 +10,14 @@ import { isRetryableRunnerError } from '../runner-error-classification.ts';
1010
import type { RunnerLogAttempt } from '../runner-failure-diagnostics.ts';
1111
import { parseRunnerResponse } from '../runner-exchange.ts';
1212

13-
test('parseRunnerResponse preserves runner unsupported-operation codes', async () => {
13+
test('parseRunnerResponse keeps the keyboard-dismiss refusal under the code the command reports', async () => {
1414
const response = new Response(
1515
JSON.stringify({
1616
ok: false,
1717
error: {
18-
code: 'UNSUPPORTED_OPERATION',
19-
message: 'Unable to dismiss the iOS keyboard without a safe native dismiss control',
18+
code: 'KEYBOARD_DISMISS_UNAVAILABLE',
19+
message:
20+
'Unable to dismiss the keyboard: it exposes no dismiss key, and background taps are never attempted (no tap outside the keyboard can be proven side-effect-free)',
2021
},
2122
}),
2223
);
@@ -26,8 +27,12 @@ test('parseRunnerResponse preserves runner unsupported-operation codes', async (
2627
() => parseRunnerResponse(response, session, runnerLogAttempt('/tmp/runner.log')),
2728
(error: unknown) => {
2829
assert.ok(error instanceof AppError);
30+
// The runner's own code stays off the wire: `keyboard dismiss` keeps refusing with the code it
31+
// always refused with, and the reason is what tells the two ways the keyboard stays up apart.
2932
assert.equal(error.code, 'UNSUPPORTED_OPERATION');
30-
assert.match(error.message, /Unable to dismiss the iOS keyboard/i);
33+
assert.equal(error.details?.reason, 'keyboard_dismiss_unavailable');
34+
assert.equal(error.details?.runnerErrorCode, 'KEYBOARD_DISMISS_UNAVAILABLE');
35+
assert.equal(error.details?.dispatched, 'no');
3136
return true;
3237
},
3338
);
@@ -40,8 +45,9 @@ test('parseRunnerResponse surfaces the keyboard-dismiss hint naming the occlusio
4045
JSON.stringify({
4146
ok: false,
4247
error: {
43-
code: 'UNSUPPORTED_OPERATION',
44-
message: 'Unable to dismiss the iOS keyboard without a safe native dismiss control',
48+
code: 'KEYBOARD_DISMISS_UNAVAILABLE',
49+
message:
50+
'Unable to dismiss the keyboard: it exposes no dismiss key, and background taps are never attempted (no tap outside the keyboard can be proven side-effect-free)',
4551
hint,
4652
},
4753
}),
@@ -54,9 +60,6 @@ test('parseRunnerResponse surfaces the keyboard-dismiss hint naming the occlusio
5460
assert.ok(error instanceof AppError);
5561
assert.equal(error.code, 'UNSUPPORTED_OPERATION');
5662
assert.equal(error.details?.hint, hint);
57-
assert.match(String(error.details?.hint), /tap_keyboard_occludes_target/);
58-
assert.match(String(error.details?.hint), /center stays above the keys/i);
59-
assert.match(String(error.details?.hint), /keyboard enter/i);
6063
return true;
6164
},
6265
);

0 commit comments

Comments
 (0)