Use correct classname for nested Navigation Link container #29380
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Size Change: +26 B (0%) Total Size: 1.39 MB
ℹ️ View Unchanged
|
|
🎉 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
As described in #21444, the container within Navigation Link inner block container was using the same class name as the parent Navigation Block. This sets the correct class, and updates the relevan style definitions to use that class as well.
This PR also moves some styles that are specific to Navigation Link, but were defined within the Navigation Block's styles.
How has this been tested?
ulblock lists have the classwp-block-navigation-link__containerinstead ofwp-block-navigation__container.Screenshots
Types of changes
Checklist: