feat(radio): adding new colors, type, and size tokens, invalid state, WHCM#3555
Conversation
🦋 Changeset detectedLatest commit: a6365c3 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
File metricsSummaryTotal size: 1.37 MB*
radio
* An ASCII character in UTF-8 is 8 bits or 1 byte. |
|
🚀 Deployed on https://pr-3555--spectrum-css.netlify.app |
8dee413 to
a46599d
Compare
d5e72d4 to
0f14273
Compare
0704a09 to
63b2cc9
Compare
3499231 to
ad861d0
Compare
8e3b47f to
75c6f2b
Compare
jawinn
left a comment
There was a problem hiding this comment.
Nice work. Visually everything is looking good to me.
Just a few suggestions here that are mostly Storybook related.
There was a problem hiding this comment.
Nice work on this! The tokens look good! I'm glad we double checked the error state and those negative tokens that were mentioned in the Figma specs.
This is another suggestion, and doesn't block an approval, but it was a thought I had. We could add some more test cases to make sure we don't miss any combination states:
- checked + hovered
- disabled + checked + hovered
- readOnly + checked +hovered
- active (to show the "down" state/perspective change, but this includes adding more to the template and an extra control)
I think some of these (or similar) are in the checkbox tests, so I was wondering if it would be helpful to expand the radio coverage in a similar way.
|
|
||
| Updates: | ||
|
|
||
| - Now has an invalid/error state |
There was a problem hiding this comment.
In that thread on slack when we asked about the red error border color, it sounded to me like those negative tokens called out in the radio Figma specs were incorrectly added. We should probably delete all of the new invalid CSS and the changeset mentions 😭
There was a problem hiding this comment.
@aramos-adobe I think you already deleted most of the invalid CSS, but I found just a couple instances of some invalid stuff here in the changeset, and then an arg in the stories file. 👍
| ".spectrum-Combobox--quiet .spectrum-Combobox-textfield.is-readOnly.is-disabled .spectrum-Combobox-input:read-only", | ||
| ".spectrum-Combobox--quiet .spectrum-Combobox-textfield.is-readOnly.is-invalid > .spectrum-Combobox-input:read-only", | ||
| ".spectrum-Combobox--quiet.spectrum-Combobox--sizeL", | ||
| ".spectrum-Combobox--quiet.spectrum-Combobox--sizeM", |
There was a problem hiding this comment.
I wonder if this snuck in during a rebase? I don't remember seeing a combobox diff before.
| label: "Label", | ||
| isEmphasized: false, | ||
| isChecked: false, | ||
| isInvalid: false, |
marissahuysentruyt
left a comment
There was a problem hiding this comment.
I think this just needs to be built again to update the metadata for radio & combobox (I'm getting metadata updates when I run this locally on my end!), but it's looking great! Thanks for all your hard work on this!
| testHeading: "Checked", | ||
| isChecked: true, | ||
| }, | ||
| { |
There was a problem hiding this comment.
Love this test expansion 💃

Radio S2 Migration
Updates:
New tokens
--spectrum-radio-invalid-color-default--spectrum-radio-invalid-color-hover--spectrum-radio-invalid-color-down--spectrum-radio-invalid-color-key-focus--spectrum-radio-border-width--spectrum-radio-text-font-weight--spectrum-radio-text-font-styleModified tokens
--spectrum-radio-emphasized-accent-color--spectrum-radio-emphasized-accent-color-hover--spectrum-radio-emphasized-accent-color-down--spectrum-radio-emphasized-accent-color-focusValidation steps
Regression testing
Validate:
Screenshots
To-do list