-
Notifications
You must be signed in to change notification settings - Fork 196
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
fix: deprecate transform logical plugin for vanilla values #2437
Conversation
db55136
to
16b2453
Compare
File metricsSummaryTotal size: 3.91 MB*
Detailsaccordion
actionbutton
assetlist
breadcrumb
calendar
pagination
slider
table
treeview
* Results are not gzipped or minified. * An ASCII character in UTF-8 is 8 bits or 1 byte. |
🚀 Deployed on https://pr-2437--spectrum-css.netlify.app |
16b2453
to
a616a88
Compare
c5088bd
to
b6ca989
Compare
5c7b874
to
a264d53
Compare
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.
Just the one comment for discussion.
a264d53
to
27a90a7
Compare
a344bf1
to
5f13e56
Compare
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.
I went through the validation links, and the ones that I've left unchecked seem to have chevrons that are either pointing the incorrect direction in the LTR state, or in the RTL state, or both.
I think maybe we're missing the rotate()
portion of the transform
on some of those?
5f13e56
to
150a8ac
Compare
56309e2
to
11b2b33
Compare
11b2b33
to
636b9e0
Compare
71197ec
to
e841a6b
Compare
addd693
to
24bfc05
Compare
24bfc05
to
a7181f1
Compare
Description
Transform logical is currently converting values to rtl versions when a special keyword is provided. This is useful however, because it involves adding a non-(browser-)specified keyword to transforms, causes more confusion when onboarding than it helps.
This PR proposes removing the transform-logical utility in favor of hardcoding the values for better clarity for contributors.
How and where has this been tested?
Should result in no rtl regressions for the following components:
Regression testing
Validate:
To-do list