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
fix(navigation-block): reduce subnavigation arrow padding #24200
fix(navigation-block): reduce subnavigation arrow padding #24200
Conversation
Edit: I tested both navigation blocks -> horizontal and vertical. |
ae5a1ad
to e72c60d
Compare
Hi @talldan, @Soean, @ajitbohra - Just wanted to ask if someone can have a look. :-) Thank you! |
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.
The units used for padding have changed since this PR was opened: we're now using em
instead of px
. That's what is causing the merge conflicts btw 😅 . Best approach is to rebase master and then convert your changes to em
.
@@ -29,6 +29,9 @@ | |||
// Styles for submenu flyout | |||
.has-child { | |||
$navigation-vertical-padding: $grid-unit-10 * 0.75; | |||
> a { |
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.
If you target .wp-block-navigation-link__content
instead of a
in this file, it will apply to both editor and front end, so you won't need the change in editor.scss
🙂
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.
Thank you very much! I will work on it 😄 !
e72c60d
to 709d88e
Compare
@tellthemachines Thanks a lot for your help. I rebased the project, converted the px values to em values and removed the redundant code. I have tested the whole thing again. Looks good so far. |
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.
Thanks for the quick turnaround! Looks good 🚀
@@ -28,6 +28,10 @@ | |||
// Styles for submenu flyout | |||
.has-child { | |||
$navigation-vertical-padding: $grid-unit-10 * 0.75; |
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.
Hmm, why do we need this 🤔 ? Is it used anywhere?
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.
Hi @kelin1003 The variable is actually no longer needed. It was also removed in the previous PR:
bc77362
I have now removed it too and tested everything again. So far everything looks good. Thanks!
Congratulations on your first merged pull request, @devfle! We'd like to credit you for your contribution in the post announcing the next WordPress release, but we can't find a WordPress.org profile associated with your GitHub account. When you have a moment, visit the following URL and click "link your GitHub account" under "GitHub Username" to link your accounts: https://profiles.wordpress.org/me/profile/edit/ And if you don't have a WordPress.org account, you can create one on this page: https://login.wordpress.org/register Kudos! |
Description
I currently work very intensively with full site editing. In the navigation block I noticed that the padding between the subnavigation point and the arrow icon is much too large. I have now adjusted this in the editor and on the published page.
How has this been tested?
I have built the Gutenberg plugin and installed it into my local wordpress installation. Afterwards I checked my changes in different browsers and could not find any errors. I tested it with many, few and long navigation points. I also checked on mobile viewports.
Screenshots
Before:
After:
Types of changes
Bug fix (non-breaking change which fixes an issue)
Checklist: