-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Global Styles: Update the order of pseudo selectors #3582
Global Styles: Update the order of pseudo selectors #3582
Conversation
Thanks @Mamaduka! I changed the ticket description to point to Trac-56928 since that ticket is specific to this issue/change. |
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.
This looks good, but let's include the Trac ticket link for additional context as to why the selectors are ordered as such. I can add this comment when committing, but wanted to make sure you agreed.
Also, I'm indifferent as to whether this needs to be synced to the Gutenberg plugin as that class should disappear in a few releases. But it may be good for consistency.
Co-authored-by: Jonathan Desrosiers <desrosj@users.noreply.github.com>
Thank you, @desrosj. The Trac ticket link makes sense to me, I will port changes back to the plugin for consistency 👍 |
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.
LGTM, matches the long term LoVe(F)HA rule.
Thank you, @peterwilsoncc. Now the only thing left is to cherry-pick the commit for the 6.1 branch. |
Backports changes from WordPress/gutenberg#45559
Props: @mikachan, @sabernhardt, @getdave (get_dave).
Trac ticket: https://core.trac.wordpress.org/ticket/56928
This Pull Request is for code review only. Please keep all other discussion in the Trac ticket. Do not merge this Pull Request. See GitHub Pull Requests for Code Review in the Core Handbook for more details.