Open violasong opened 6 years ago
Would love to work on this. @jasonLaster
To pick this up again, let's discuss a bit the UI and UX. @violasong It would be great if you could share any previous discussions and decisions made that resulted in your mockups.
I'll analyze those mockups a bit here first. So what I see is:
Search field replacing any existing static search fields
Suggested content and commands
Context specific content search suggestions
Panel / context information options
Panel / context related actions
Panel switching options
Commands and content search suggestions are initially shown
Options are split by category
Options have different icons depending on their type
Options may have additional information
Options may have a shortcut assigned
All options are one-off options
Options may be formatted
Sebastian
Some background: in my Feb 2020 survey, I found that folks were less excited about the Command Palette than the 6 other features I asked them about. (Of course, I wasn't asking about some kind of amazing omni-panel that also searched the codebase + MDN). The question was as follows:
Imagine that Firefox DevTools had a new command palette similar to the one in Chrome, accessible with Ctrl-Shift-P (Cmd-Shift-P on Mac). This palette would allow you to quickly navigate to files, switch to another panel, toggle settings, and find hidden-away features. Rate how much you agree with the sentence, “This would benefit my work.”
Results:
31% of Chrome users “Strongly Agreed” that a Command Palette in Firefox would benefit them compared to 23.3% of Firefox users. However, Chrome users still ranked Command Palette last when sorting it against the other features. When comparing numbers for “agree or strongly agree,” this feature got 50-60% approval, vs 80-90% for other features.
My gut feeling is that many people may find it too complicated to learn and use as part of an everyday workflow. My recommendation at the time was to postpone this feature in favor of more desired features, but that doesn't necessarily mean we shouldn't still look into this. :)
Found this on a google search just now. I would find this SUPER helpful, but tbh only if the hotkey were customizeable - I'm too used to pressing ctrl+T in sublime, pycharm, vscode, etc, that's how I'd want to access this. In fact just now when playing with it in chrome I accidentally opened about 3 new tabs 😂 I assume the context will pull away from the window, so Ctrl+shift+P remains private window when you're not focusing devtools (& same would be for any potential rebind)?
I'm here also because of Google search, and I consider this feature as very useful, I really miss this one in Firefox's devtools
Related:
Just filing this here so we have it, but it can go into some backlog :)
The idea is that eventually every DevTool panel could have access to this functionality. It would allow you to switch between panels, as Chrome's command menu does. Debugger and Inspector examples: https://mozilla.invisionapp.com/share/39IG53NDEW7#/288014318_commandmodal