-
-
Notifications
You must be signed in to change notification settings - Fork 78.8k
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
Simpler custom control markup #25174
Comments
For example: Please note that the pull request changes the semantic meaning of The default in _variables.css would be updated to 0.5rem instead of 1.5rem if this request was applied I imagine. |
Hmm, this might be doable. I played with flexbox styles on the checkboxes before I rewrote them for Beta 3, but I couldn't make it work well. With the reduced markup, this gets easier. Lemme try this out on both the default and custom checks. |
Only downside I see to this is, within the same form there being inconsistent spacing should your radio and checkbox be different dimensions. I don't know off the top of my head if they are yet, but I'll take a look shortly. |
- Removes absolute positioning and relies on flexbox for input+label layout and spacing - Adjusts the gutter variables to be true gutters, not gutters plus space for input - Updates inline variants accordingly This is an implementation of #25174, and a more complete attempt than #25175 at implementing it across all our checks.
Fresh pass for both input types at #25184. |
I was playing around with making sizing available to custom radio/checkboxes, and figured that rather than using |
I started playing with some new stuff again for v5, but I don't think we'll be significantly changing the markup here. See the Codepen I put together. In both of your modification, the reduced Closing this out and slating some stuff for v5 though which will ideally combine those native and default checks for a lighter codebase and easier customization. |
I was running into issues with the custom-control (input and checkbox) padding and generally just not being as friendly as I would have liked.
Instead of padding-left:1.5rem, why not padding-left:1rem, and then create margin-left:0.5, which allows for the checkbox itself to be rendered cleanly. Useful for me when putting a checkbox into a container (say, a
<td>
of a<table>
) and want it to look clean and centered. Obviously I could just create my own class here, but I feel that this type of styling is more clean.Where possible, I like to stay away from position: absolute when creating something meant to be extending/used globally (e.g., the bootstrap library :) ). One benefit of avoiding absolute is that sizing the custom input becomes a little easier, because all you need to worry about at that point is the top offset (instead of having to worry about the padding-left spacing to make room for the absolute)
Anyway, I've put my ideas here:
https://jsfiddle.net/fqxcdp8h/
I hope you would at least consider implementing the fix for
#1
.The text was updated successfully, but these errors were encountered: