Skip to content

Show platform-specific shortcut hints and button tooltips #10

Description

@user-github-me

User problem

The workbench currently displays macOS Command symbols and combined Mac/Windows
shortcut hints. Windows users should see familiar Ctrl shortcuts for their system.

Acceptance criteria

  • Show Command (⌘) hints on macOS and Ctrl hints on Windows/Linux.
  • Adapt the Intercept, Repeater, Decoder, and tool-switcher shortcut text.
  • Adapt button tooltips and accessible shortcut metadata consistently.
  • Use the browser's platform information with a local fallback.
  • Remove the Command-key symbol from the unrelated Decoder navigation icon.
  • Preserve working Ctrl/Command keyboard bindings and version 1.1.0.
  • Verify Mac and Windows rendering in the browser, including tooltips.

Implementation status

Implemented and verified in PR #1 on feat/v1.1-workbench. PR #1 was merged into main on 2026-10-03, merge commit eeb65009fa6e343cf6dd1f67386be0afc5bbb3e5. GitHub automatically closed this issue as completed through the PR's closing reference. The source changes are now on main; the Chrome Web Store release remains pending.

Verification

The browser integration checks native platform detection and simulated macOS,
Windows, Linux, MacIntel and macOS fallback values across all hints, tooltips and
ARIA shortcut metadata. Both Ctrl+K and Command+K still open the tool switcher.
All existing browser scenarios and 29 Node tests pass, as do syntax and patch
format checks. The runtime-only ZIP remains v1.1.0.

Completion record

The implementation commits are 7b76001, 3ee1668, 4f1d89c, 504051e, and test follow-up 619736d. Relevant verification is described above and in PR #1. All 29 Node regressions and JavaScript syntax checks pass; GitHub CI passes on Node 22. The workbench/browser features were checked with isolated local HTTP/WebSocket fixtures; shortcut labels were also checked for Mac/Windows/Linux platforms. The maintainer merged PR #1, and GitHub closed this issue automatically; new bugs or follow-up scope should use a separate issue, or reopen this one if its original criteria fail.

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    accessibilityBarrier affecting people with disabilitiesbugSomething isn't working

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions