Skip to content

fix: HotKeyRecorderField stays first responder after successful capture (L3) #49

Description

@sfegette

Summary

In HotKeyRecorderField.handle(_:), after Escape the view correctly calls window?.makeFirstResponder(nil). After a successful hotkey capture, however, the view stays first responder — leaving the recorder in a visually active state when the user expects it to be done.

Fix

After onCapture?(...) is called, add:

window?.makeFirstResponder(nil)

Notes

Consistent with the Escape path — the recorder should resign after any terminal event (cancel or capture).

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions