WordPress / WordPress/gutenberg
Command Palette shows redundant commands for current context
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 11.8k
- Forks
- 4.9k
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 524
Description
Description
When using the Command Palette, commands for navigating to the current screen/context are still displayed.
For example:
If you are already in the Navigation screen, the Command Palette still suggests “Go to Navigation.”
Similarly, in other screens (e.g., Posts, Pages, Templates, Dashboard), “Go to [current screen]” is listed as an option.
This creates unnecessary noise and reduces the usefulness of the Command Palette by showing actions that have no effect.
Steps to Reproduce
- Goto admin/editor area in your site.
- Navigate to a specific area, e.g., Navigation.
- Open the Command Palette (Cmd + K / Ctrl + K).
- Search for “Navigation."
Actual Behavior
The palette suggests “Go to Navigation,” even though the user is already there.
Expected Behavior
Commands to navigate to the current context should be hidden or deprioritised, as they are redundant.
Environment
- WordPress site setup with Gutenberg 21.5+
- Browsr: Chrome
Impact :
- Adds visual clutter.
- May confuse users who expect results to be context-aware.
Screencap
https://github.com/user-attachments/assets/3306e549-6a83-4ddf-aeea-664027e7788c
@t-hamano Due to limited access to the repo, I can not tag the issue, but this is not a bug; it is something we can consider as an improvement.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the issue in the admin/editor Command Palette with Cmd + K or Ctrl + K, especially on Navigation, Posts, Pages, Templates, and Dashboard. Trace how the “Go to [current screen]” commands are provided, then verify that commands for the current context are hidden or deprioritised without removing navigation to other contexts.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100