-
Notifications
You must be signed in to change notification settings - Fork 4.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove default entry into Navigation Menu focus mode but retain ability to access via "Edit" #61275
Conversation
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.
To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
Size Change: +72 B (0%) Total Size: 1.74 MB
ℹ️ View Unchanged
|
@scruffian @draganescu Will you be able to shepherd this over the line? I ask because I see a lot of movement happening in |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This works great and the code is straightforward! 👏🏻
return { | ||
key: 'styles', | ||
key: 'navigation', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What was going on here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Typo from someone I expect. I've seen in corrected in other (yet to be merged) PRs.
Yeah this is a good compromise :) thanks :) |
Screen.Recording.2024-05-03.at.9.52.21.AM.movFound a bug when clicking on custom links. They open the link popover and then disappear from the list. Update: This is not related to this PR. It happens on Trunk too. |
a95b5c1
to
32ab6a9
Compare
Flaky tests detected in 32ab6a9. 🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/8941146177
|
What?
Removes the default behaviour of navigating to the navigation focus mode editor when clicking on a single Navigation Menu in the "Site Hub" (left hand black sidebar). Instead remains showing the full editor canvas.
Retains the ability to access the navigation menu focus mode via a new
Edit
option to the Navigation Menu's options.This PR is an alternative to #59340. I did try to work on that PR but it had diverged from
trunk
and so - having confirmed with @draganescu - it made sense to start afresh.Co-authored-by: Andrei Draganescu [email protected]
Co-authored-by: Rich Tabor [email protected]
Why?
During the discussion in #59340 contributors raised valid concerns regarding the utility of the focused navigation menu edit mode. Principally some contributors utilise this to edit menus which are not currently used within a Template (which incidentally is exactly why it exists!).
Therefore this PR does not remove the ability to edit a Navigation Menu in the focused editor mode, but rather deprioritises it in the default UX of interacting with
Navigation
in the Site Hub sidebar.How?
Now when clicking on a single Navigation Menu you are shown the details of that menu in the siderbar but the editor canvas does not enter "focus mode". This avoids the confusion that has been associated with this view which is really aimed at more advanced use cases.
The ability to access the Navigation Menu in focus mode is retained via the addition of an
Edit
link in the Navigation Menu's options menu.Testing Instructions
Edit
option.Testing Instructions for Keyboard
Screenshots or screencast
Screen.Capture.on.2024-05-01.at.10-59-07.mp4