-
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
Navigation Block: Text settings not working #23258
Comments
@alaczek I couldn't find those text settings. It might be that they're provided by a plugin you have active? |
Hmm, that is strange. I deactivated all plugins aside from Gutenberg, and still, those settings for Navigation block were available. Maybe we need a third pair of eyes :) |
@talldan @alaczek I tested this and could see the text settings. You need to select the entire block in order to see these settings. Here's a video replicating this: https://cloudup.com/c2uXL_JKGfG Of note, it's pretty confusing how different the block settings screen is when selecting the entire block vs when you are working within the block itself.
Removing the needs-testing tag! |
Updating Default style will save your preference for future navigation blocks e.g. if you select dark and add one more navigation block it will be dark. I'm not sure this is the best place to be making this decision. I was confused as to what needs to happen and it took me some time to figure it out. |
Thanks, I see it happening now 👍 |
Why is there a font family in the first place? |
Site Navigation block offers some Text settings in the sidebar, but they seem to have no effect on either editor or the front end.
To reproduce
Steps to reproduce the behavior:
This seems to be because of the following styles applied to the
span
element via.wp-block-navigation-link__label
class, which override the theme styling:Screenshots
![rrluEbZ6Oy](https://user-images.githubusercontent.com/4550351/84963579-1e77fe80-b14d-11ea-8827-b0dcf90417c5.gif)
Editor version (please complete the following information):
The text was updated successfully, but these errors were encountered: