Keyboard shortcuts¶
Browser commands¶
The manifest declares two commands. Both are handled by the service worker (browser.commands.onCommand, decision 90):
| Command | Suggested key | Action |
|---|---|---|
picker-start |
Alt+Shift+P | Start the element picker in the active tab |
picker-pause |
Alt+Shift+Space | Pause the running picker, or resume it on the next press |
A command acts only when all of these hold. Otherwise it does nothing and shows no message:
- Author mode is on (extension options).
- The active tab is an http or https page.
- The extension has access to that tab's site, by a grant from you or by managed policy.
- For
picker-pause, a picker is already running in that tab.
picker-start starts the element mode, the same as the side panel's Pick element button. A pick is delivered to the studio field that asked for it, so open the studio on the item you are editing first; the shortcut is for re-arming the picker without moving to the side panel. Pausing hides the highlight and lets clicks through to the page; resuming restores picking. A page reload re-injects the picker unpaused.
Change the keys on chrome://extensions/shortcuts (or edge://extensions/shortcuts).
While the picker is running¶
The picker script handles its own keys on the page:
| Key | Action |
|---|---|
| Esc | Stop picking |
| Alt+Shift+Space | Pause or resume picking, when the browser passes the key to the page |
Gotchas¶
- Chrome may show a declared command as unassigned if the suggested key collides with another extension.
- While the command is assigned, the browser takes Alt+Shift+Space before the page sees it, so the worker handles it. The in-page handler is the fallback when the command is unassigned.
- Pause state lives in
storage.sessionfor the tab and is cleared when the picker stops, restarts or the tab closes.