Keyboard shortcuts do not conflict with common browser or system defaults
Why it matters
Extension shortcuts that collide with Chrome-reserved combinations (Ctrl+T, Ctrl+W, Ctrl+Shift+N, Ctrl+L, Ctrl+R, F5) get silently dropped by Chrome during registration — the manifest declares them, the extension looks configured, but the shortcut never fires. Users file bug reports about features that do not work, developers waste cycles investigating non-bugs, and support costs climb. Conflicts with OS-level shortcuts (Cmd+Space, Win+L) cannot be overridden at all and make the extension appear broken on specific platforms.
Severity rationale
High because silently dropped shortcuts create bug reports, support load, and the appearance of a broken extension.
Remediation
Use Alt+Shift+{Key} or MacCtrl+Shift+{Key} patterns in manifest.json — these bindings are reliably available to extensions on all platforms Chrome supports. Declare platform variants explicitly:
{
"commands": {
"toggle-feature": {
"suggested_key": { "default": "Alt+Shift+F", "mac": "MacCtrl+Shift+F" },
"description": "Toggle feature"
}
}
}
Verify registration in a clean Chrome profile at chrome://extensions/shortcuts.
DetectionPro
The detection method for this pattern is part of AuditBuffet Pro.
The full method (what to look for, pass and fail conditions, and how results get reported) ships inside the Extension UX & Performance Audit. The pattern definition, severity rationale, and remediation remain openly licensed under CC-BY-4.0.
Taxons
History
- 2026-04-18·v1.0.0·Initial import from extension-ux-performance·automated