-
-
Notifications
You must be signed in to change notification settings - Fork 79.1k
Styles for [input:disabled] on checkboxes and radio. Issue #17918 #17921
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
Conversation
If possible, exclude |
Also, it's not required, but you might want to associate the email address you used for your commit with your GitHub account so that you'll get credit for it in your GitHub profile page. |
Thanks for the Git help, @cvrebert, much appreciated. I have added the email to my GitHub profile (and updated git config with the preferred one so this doesn't happen again). I tried to I'd like to get this right, but don't want to waste your time if it's going to be complicated. Thank you! |
Ok I realized the commits had not been pushed. I think the commit is now correct (i.e. rm'd the dist\css files). Interested in how it looks to you, @cvrebert. Thank you! |
Doesn't quite look right. (The files I mentioned shouldn't be in the diff at all.)
Nah, that's all right. We can fix it on our end when merging this.
To update the author info, you'd need to do |
Thanks for the info, Chris. I will have a go at updating the email tomorrow when back in the office. |
@@ -83,6 +83,10 @@ | |||
background-image: url(data:image/svg+xml;base64,PD94bWwgdmVyc2lvbj0iMS4wIiBlbmNvZGluZz0idXRmLTgiPz4NCjwhLS0gR2VuZXJhdG9yOiBBZG9iZSBJbGx1c3RyYXRvciAxNy4xLjAsIFNWRyBFeHBvcnQgUGx1Zy1JbiAuIFNWRyBWZXJzaW9uOiA2LjAwIEJ1aWxkIDApICAtLT4NCjwhRE9DVFlQRSBzdmcgUFVCTElDICItLy9XM0MvL0RURCBTVkcgMS4xLy9FTiIgImh0dHA6Ly93d3cudzMub3JnL0dyYXBoaWNzL1NWRy8xLjEvRFREL3N2ZzExLmR0ZCI+DQo8c3ZnIHZlcnNpb249IjEuMSIgaWQ9IkxheWVyXzEiIHhtbG5zPSJodHRwOi8vd3d3LnczLm9yZy8yMDAwL3N2ZyIgeG1sbnM6eGxpbms9Imh0dHA6Ly93d3cudzMub3JnLzE5OTkveGxpbmsiIHg9IjBweCIgeT0iMHB4Ig0KCSB3aWR0aD0iOHB4IiBoZWlnaHQ9IjhweCIgdmlld0JveD0iMCAwIDggOCIgZW5hYmxlLWJhY2tncm91bmQ9Im5ldyAwIDAgOCA4IiB4bWw6c3BhY2U9InByZXNlcnZlIj4NCjxwYXRoIGZpbGw9IiNGRkZGRkYiIGQ9Ik0wLDN2Mmg4VjNIMHoiLz4NCjwvc3ZnPg0K); | |||
@include box-shadow(none); | |||
} | |||
|
|||
input:disabled ~ .c-indicator { | |||
background-color: #bbb; |
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.
Should probably use a variable for this color
I did wonder that and I'll take a look. Thanks for your patience, Chris. I have used open source software for years and this is my first meaningful contribution to a project, so I am happy to make the effort to get it right. If I make a change to use a variable, would it be a new commit/push (referencing this issue number?) |
No problem! 😄 Thanks for giving back to the community ❤️ The variable declaration should be added to
Yes, that'd be fine. |
I'll include the doc changes in the commit, but that is probably the most subjective part because you might not like the wording. Ideally, I would show you a diff of the changes for review prior to committing. How best to achieve this? |
Eh, you might as well just commit your suggestion and then depending on the feedback either you can push more fixup commits or we can fix it ourselves when we go to merge it. In any case, we'll squash it into a single commit on our end when we merge this PR. |
Thanks once again, Chris. I'll add the doco commit later when I can test (Jekyll setup is problematic on this machine.) |
@@ -83,6 +83,11 @@ | |||
background-image: url(data:image/svg+xml;base64,PD94bWwgdmVyc2lvbj0iMS4wIiBlbmNvZGluZz0idXRmLTgiPz4NCjwhLS0gR2VuZXJhdG9yOiBBZG9iZSBJbGx1c3RyYXRvciAxNy4xLjAsIFNWRyBFeHBvcnQgUGx1Zy1JbiAuIFNWRyBWZXJzaW9uOiA2LjAwIEJ1aWxkIDApICAtLT4NCjwhRE9DVFlQRSBzdmcgUFVCTElDICItLy9XM0MvL0RURCBTVkcgMS4xLy9FTiIgImh0dHA6Ly93d3cudzMub3JnL0dyYXBoaWNzL1NWRy8xLjEvRFREL3N2ZzExLmR0ZCI+DQo8c3ZnIHZlcnNpb249IjEuMSIgaWQ9IkxheWVyXzEiIHhtbG5zPSJodHRwOi8vd3d3LnczLm9yZy8yMDAwL3N2ZyIgeG1sbnM6eGxpbms9Imh0dHA6Ly93d3cudzMub3JnLzE5OTkveGxpbmsiIHg9IjBweCIgeT0iMHB4Ig0KCSB3aWR0aD0iOHB4IiBoZWlnaHQ9IjhweCIgdmlld0JveD0iMCAwIDggOCIgZW5hYmxlLWJhY2tncm91bmQ9Im5ldyAwIDAgOCA4IiB4bWw6c3BhY2U9InByZXNlcnZlIj4NCjxwYXRoIGZpbGw9IiNGRkZGRkYiIGQ9Ik0wLDN2Mmg4VjNIMHoiLz4NCjwvc3ZnPg0K); | |||
@include box-shadow(none); | |||
} | |||
|
|||
input:disabled ~ .c-indicator { | |||
background-color: $custom-form-bg-color-disabled; |
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.
Properties should be ordered color, background-color
} | ||
~ .c-indicator-label { | ||
color: $custom-form-label-color-disabled; | ||
cursor:not-allowed; |
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.
Colon after property should be followed by at least one space
|
||
input:disabled { | ||
~ .c-indicator { | ||
background-color: $custom-form-bg-color-disabled; |
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.
Properties should be ordered cursor, background-color
background-color: $custom-form-bg-color-disabled; | ||
} | ||
~ .c-indicator-label { | ||
cursor: not-allowed; |
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.
Properties should be ordered color, cursor
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.
Properties should be ordered color, cursor
Hello Chris, me again. While I have tested every change prior to commit, I clearly haven't linted. Sorry for the hound spam. Lesson learned. Can I just check whether you are likely to be happy with wrapping the checkbox/radio label in a span? This is in order to apply the before:
after:
I tend to think the cleaner the html the better, but I see the value either way. I'm curious which way you'd want to go. |
Those sorts of design specifics regarding the custom form widgets are @mdo's department rather than mine. |
Changes from here are now part of #18771 (squashed and rebased there). Thanks! |
Thanks @mdo, it's great to have made even a small contribution. Will I be famous and show up as a contributor? (I'm a simple man 😊) |
Hah, yeah, you'll be on the contributors list once the |
Fixes #17918.