-
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
FormToggle: do not use "/" math operator #56672
Conversation
Probably there's no need for a CHANGELOG entry, if this is part of the same Gutenberg release. |
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.
Green check from me, but I saw a comment by @andrewhayward so I'll defer to him if he prefers another path forward.
Yup, Andrew suggested a cleaner solution — just updated the PR to implement his suggestion |
Size Change: 0 B Total Size: 1.72 MB ℹ️ View Unchanged
|
Flaky tests detected in 9cc302f. 🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/7044611846
|
I'm not overly concerned which approach we use, but going the recommended route is probably better for future-proofing.
Agreed. Do we ever tack two PRs together in the same CHANGELOG entry? Would at least make it clear that they're both relevant.
|
Thanks for the quick follow-up! 🙇 |
* FormToggle: do not use "/" math operator * Use math.div * CHANGELOG
What?
Refactor
FormToggle
's styles away from using the/
math operatorWhy?
As flagged in #56515 (comment), the
/
operator is deprecated in SassHow?
Using the
math
module and themath.div
operator (as suggested here)Testing Instructions
FormToggle
renders correctly in Windows High Contrast Mode