Skip to content

fix: multiple :not() classes#62470

Closed
chrisbellboy wants to merge 1 commit intoWordPress:trunkfrom
chrisbellboy:fix/root-padding-css
Closed

fix: multiple :not() classes#62470
chrisbellboy wants to merge 1 commit intoWordPress:trunkfrom
chrisbellboy:fix/root-padding-css

Conversation

@chrisbellboy
Copy link
Copy Markdown
Contributor

See #60715

What?

Fixes multiple :not() classes

Why?

The CSS is currently not rendering due to invalid :not() implementation.

How?

By chaining the multiple :not() separately.

@github-actions
Copy link
Copy Markdown

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 props-bot label.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Co-authored-by: chrisbellboy <chrisdotdotdot@git.wordpress.org>

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

@chrisbellboy chrisbellboy mentioned this pull request Jun 11, 2024
7 tasks
@fabiankaegy fabiankaegy added [Type] Bug An existing feature does not function as intended Backport to WP Beta/RC labels Jun 11, 2024
@chrisbellboy
Copy link
Copy Markdown
Contributor Author

Closing as TIL that :not() does allow multiple classes in a single selector since CSS Selectors Level 4 🤓

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

[Type] Bug An existing feature does not function as intended

Projects

No open projects
Status: ✅ Done

Development

Successfully merging this pull request may close these issues.

3 participants