-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Navigation: Try to improve the appender in an empty block #43115
Conversation
Size Change: +4 B (0%) Total Size: 1.27 MB
ℹ️ View Unchanged
|
This PR will need a rebase and slight change in direction based on #43169. |
564b80a
to
7b55b3b
Compare
This has been rebased and is now vastly simpler because of #43169 landing: |
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.
👍 Looks good to me. This is what I saw during my testing.
Empty menu
trunk
try/nav-setup-polish
Other Results
The rest of the results are identical between trunk and this branch.
What?
When you create a new navigation menu (Switch menu > Create menu at the moment), you get a big black plus:
This PR fixes that by scoping some rules and moving some code around, and also fixes the black plus:
There's an opportunity for a better fix there, as the nav block at the moment uses the "button block appender". It does this so that the appender can be permanently visible in submenus (see #37572 for more conversation). But this is a divergence that would be good to revisit.
Testing Instructions
Please test the nav block with empty, full menus, submenus, with and without responsive.
Edit: Updated description per new goals as of #43115 (comment)