Repository navigation
Source Inspector: Shift+Cmd/Ctrl+Click shortcut conflicts with macOS screenshot (should be configurable) #374
Description
Problem
The Source Inspector ("Go to source") is triggered by Shift + Cmd (Meta) + Click, which is hardcoded in source-inspector.tsx:
const isShiftHeld = keys.includes('SHIFT')
const isCtrlHeld = keys.includes('CONTROL')
const isMetaHeld = keys.includes('META')
return isShiftHeld && (isCtrlHeld || isMetaHeld)On macOS, Shift + Cmd + 4 is the system screenshot shortcut (region capture). When you press Shift + Cmd to start a screenshot, the Source Inspector immediately activates and highlights elements under the cursor — the highlight overlay ends up captured in the screenshot.
This is a pretty common workflow conflict since virtually every Mac user uses Shift+Cmd+4 regularly.
Proposed Solution
Make the Source Inspector modifier keys configurable via the Vite plugin options, e.g.:
devtools({
injectSource: {
enabled: true,
modifierKeys: ['Alt', 'Shift'], // default: ['Shift', 'Meta'] or ['Shift', 'Control']
},
})The current hardcoded Shift + Meta/Ctrl default is fine, but users should be able to change it to avoid conflicts with OS-level shortcuts.
Environment
- macOS (Apple Silicon)
@tanstack/devtools-vite- Affects any Mac user who takes screenshots with Shift+Cmd+4
Reacted by Ben Senescu
Activity
github-actions commentedon Mar 9, 2026
Hi @ethan-huo, thanks for the detailed write-up! The conflict with macOS's Shift+Cmd+4 screenshot shortcut is a clear and well-explained issue, and the proposed configurable modifier keys solution makes a lot of sense.
Before we can triage this further, could you fill in a few details that are required by our bug report template?
@tanstack/devtools-viteare you using? (e.g.v0.x.x, not just "latest")Thanks!
bensenescu commentedon Mar 11, 2026
Huge +1 on this ^^^^
I started this PR on it, but couldn't figure out how to reliably trigger the inspector with other hot keys on mac: bensenescu#1
harry-whorlow commentedon Mar 19, 2026
@ethan-huo what version are you using? we've pushed out a couple fixes to try address this.
bensenescu commentedon Apr 7, 2026
@harry-whorlow
I'm still seeing this after updating. Here are my versions: