-
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
Merge 63406 (Navigation block: Allow themes to override block library text-decoration rule) into wp/6.6 branch #63641
Conversation
…ion rule (#63406) * Reduce specificity of navigation text decoration rule * Apply Aaron suggestion to also lower specificity for focus/active * Remove `:not([class*="has-text-decoration"])` from selector ---- Co-authored-by: talldan <[email protected]> Co-authored-by: ellatrix <[email protected]> Co-authored-by: aaronrobertshaw <[email protected]>
Size Change: -49 B (0%) Total Size: 1.75 MB
ℹ️ View Unchanged
|
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 wrangling this one @andrewserong 👍
✅ Code changes match #63406
✅ Nav block text decoration tests well in both editor and frontend
LGTM 🚢
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. |
Not all that familiar with the CSS specificity work but I I followed the testing steps in #63406 and it functioned as expected 👍 |
It's auto cherry-picked, but thanks for the PR and approvals! |
What?
This PR proposes merging "Navigation block: Allow themes to override block library text-decoration rule (#63406)" into the
wp/6.6
branch.Why?
A separate PR is used here so that we have a clean build of the
wp/6.6
branch with this change applied on top of it, and can download a zip file of the generated artefact.How?
Checked out the
wp/6.6
branch, and cherry picked the merge commit from #63406 into this branch.Testing Instructions
Follow the testing instructions in #63406