Repository navigation
DevTools debugger should support keyboard shortcuts for stepping #3867
Description
Activity
- addeddevtools-debugger-screenIssues with the Debugger screenIssues with the Debugger screenobservatory: missing core functionalityCore features implemented in Observatory that aren't in DevToolsCore features implemented in Observatory that aren't in DevToolsobservatory migrationRelated to the Observatory -> DevTools migration effortRelated to the Observatory -> DevTools migration effort
on Mar 15, 2022 - changed the title
[-]The DevTools should support keyboard shortcuts for stepping[/-][+]DevTools debugger should support keyboard shortcuts for stepping[/+]on Mar 15, 2022 - addedgood first issueGood issues for new contributorsGood issues for new contributors
on May 30, 2023 - addedP3issues we think are valid but not importantissues we think are valid but not importantand removed
on Jul 5, 2023 This could also help if using a CLI IDE such as opencode or Claude Code.
How can I help testing this fix? I'm actively working on my own Flutter app as a startup founder.Hi @lapc506 - thanks for reaching out! The debugger panel currently handles the following keyboard events (
cmd/ctrl+Shift+Pto open the file selector,cmd/ctrl+fto search in a file).If you want to take this on, I would suggest adding the following keyboard shortcuts:
- Pause / Resume:
F8 - Call stack navigation (next / previous frame):
F9 - Step Over:
F10 - Step In:
F11 - Step Out:
Shift+F11
F10,F11andShift+F11are all used for step over/in/out by VS Code and Chrome DevTools. VS Code has no equivalent for next frame, and usesF5for Pause / Resume. But I think it is best for these keyboard shortcuts to be numerically sequential, which is why I prefer Chrome DevToolsF8andF9here.As a side-note: It would be nice if the Pause / Resume and Step Over shortcuts worked for the floating debugger controls (see screenshot) as well, but that can be addressed later.

- Pause / Resume:
See Observatory -> DevTools Tracking Issue.
Observatory allows for users to interact with its debugger via console commands, supporting various stepping flavors. If we'd prefer to avoid having a debugger "console" we should at the very least have keyboard shortcuts for the following operations: