-
Notifications
You must be signed in to change notification settings - Fork 794
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
Add PlanRadioButton Component #14025
Conversation
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.
@robertf4 Thank you for extracting this presentational component to a separate PR. I left some feedback regarding the CSS.
I know you've got a lot on your plate right now, so if you need any support in addressing the feedback, feel free to reach out to me.
@@ -0,0 +1,11 @@ | |||
.plan-radio-button__input { | |||
margin-left: -20px !important; |
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 don't think we need to use an !important
rule here. I guess it's enough to increase the specificity of the selector by changing it to something like:
input[radio].plan-radio-button__input {
I'm wondering, though, if setting a display: flex
layout on the parent element (.plan-radio-button__label
) and then getting rid of the negative margin hack altogether wouldn't make more sense. What do you think?
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.
Agreed, much cleaner. Updated.
ab4bdd8
to
cb3d878
Compare
cb3d878
to
c4fc050
Compare
8fbc2b1
to
bc5e3fe
Compare
This is an automated check which relies on |
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.
Thanks for updating the code. Looks good to me now. I think it's ready to merge.
Changes proposed in this Pull Request:
Is this a new feature or does it add/remove features to an existing part of Jetpack?
See the P2 here for the design of this PR: p1HpG7-7MK-p2 (specifically the part titled "WP Admin Desktop")
See the P2 here for the overall MT: p1HpG7-7ET-p2
Testing instructions:
This cannot be tested on its own here. Use #14018 to test.
Proposed changelog entry for your changes: