Skip to content

fix: say why a key has no receiver and point to the menu #14

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
iamnbutler merged 1 commit into from
Oct 15, 2026
Merged

fix: say why a key has no receiver and point to the menu #14

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 4 additions & 1 deletion native/sources/client/actions.swift
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -223,7 +223,10 @@ func nativeAction(_ client: PeekabooBridgeClient) async throws -> Data {
guard observed.knownIsEnabled != false else { throw ActionError("The observed element is disabled.") }
}
if request.op == .key || request.op == .insert, context.focusedElement == nil {
throw ActionError("The snapshot has no exact focused control. Click a control, then inspect the window again.")
// Peekaboo resolves keyboard receivers from the window's focused element; without one the key has no target.
throw ActionError(request.op == .key
? "The snapshot has no exact focused control, so this key has no verified receiver. If the command is in a menu, use the menu instead. Otherwise click the control that should receive the key, inspect the window again, and check that the new snapshot reports a focused element before retrying."
: "The snapshot has no exact focused control. Click the text field, then inspect the window again.")
}
if request.op == .insert {
// The GUI owns the snapshot lease and clipboard transaction through consumption and cleanup.
Expand Down
Loading