Skip to content

fix(super-key): say when macOS refuses the keyboard tap - #1951

Open
PathGao wants to merge 1 commit into
vorssaint:mainfrom
PathGao:fix/super-key-report-tap-failure
Open

PathGao wants to merge 1 commit into
vorssaint:mainfrom
PathGao:fix/super-key-report-tap-failure

Conversation

@PathGao

@PathGao PathGao commented Sep 24, 2026

Copy link
Copy Markdown
Contributor

Summary

When macOS refused to create the Super key's keyboard event tap, the service only set itself to not running. The Super key page then showed nothing at all: no "Working now" and no warning, so the key just did nothing. A refused tap is now reported through the existing mapping failure line on the page, with a new reason that tells the user to turn Vorssaint off and on under Privacy & Security › Accessibility and switch the key on again. The new string is translated in all 13 languages.

Verification

  • Apple M5, macOS 27.0.
  • ./build.sh --test: TESTS OK (61,540 checks). A new contract runs the real tap thread body with a stand-in that refuses the event tap, and checks the key stops and the page gets the new reason.
  • ./build.sh: compiles and links with 0 warnings.

A refused event tap only stopped the service, so the Super key page showed neither the working line nor a warning. It now sets a mapping failure that tells the user how to renew the Accessibility grant.
@PathGao
PathGao requested a review from vorssaint as a code owner September 24, 2026 06:17

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant