This bug is meant to implement a basic version of the command menu mentioned in bug 1603713. The menu should consist of a list of commands and a filter field which overlay the current panel. It should include the basic functionally of opening the menu via a keyboard shortcut (probably `Ctrl`+`Shift`+`P`) and the general DevTools menu. The commands list needs to be scrollable, navigatable via mouse and keyboard (and maybe touch) and filterable. The filter field should at least allow to match commands by ignoring the case and any spaces in the command's words. E.g. entering `showd` should match a command called "Show Debugger". Clicking a command or pressing `Enter` when it's selected executes it and closes the command menu. Sebastian
Bug 1603718 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
This bug is meant to implement a basic version of the command menu mentioned in bug 1603713. The menu should consist of a list of commands and a filter field which overlay the current panel. It should include the basic functionally of opening the menu via a keyboard shortcut (probably `Ctrl`+`Shift`+`P`) and the general DevTools menu. The commands list needs to be scrollable, navigatable via mouse and keyboard (and maybe touch) and filterable. The filter field should at least allow to match commands by ignoring the case and any spaces in the command's words. E.g. entering `showd` should match a command called "Show Debugger". Clicking a command or pressing `Enter` when it's selected executes it and closes the command menu. The commands that should initially be supported are one-off commands, i.e. commands that can be called directly without options. For example, those tasks may include global ones like panel navigation, preference toggling, or reloading the page as well as panel-specific actions like clearing the console or deactivate all JavaScript breakpoints. In preparation for easy extensibility, any panel-specifc commands should be registered by the panels themselves. Sebastian
This bug is meant to implement a basic version of the command menu mentioned in bug 1603713. The menu should consist of a list of commands and a filter field which overlay the current panel. It should include the basic functionally of opening the menu via a keyboard shortcut (probably `Ctrl`+`Shift`+`P`) and the general DevTools menu. The commands list needs to be scrollable, navigatable via mouse and keyboard (and maybe touch) and filterable. The filter field should at least allow to match commands by ignoring the case and any spaces in the command's words. E.g. entering `showd` should match a command called "Show Debugger". Clicking a command or pressing `Enter` when it's selected executes it and closes the command menu. The commands that should initially be supported are one-off commands, i.e. commands that can be called directly without options. For example, those tasks may include global ones like panel navigation, preference toggling, or reloading the page as well as panel-specific actions like clearing the console or deactivate all JavaScript breakpoints. In preparation for easy extensibility, any panel-specifc commands should be registered by the panels themselves. The [command palette implemented in the Debugger panel](https://developer.mozilla.org/en-US/docs/Tools/Debugger/How_to/Search) can serve as a good starting point, UI wise, and might be reused for this purpose. Sebastian