-
Notifications
You must be signed in to change notification settings - Fork 11
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
Split in 2 CSS classes (with one dedicated to color)? #5
Comments
Hello, sorry for late reply. |
All existing classes have both the notion of styling the checkbox with material design AND giving it color. When I need a new color for my checkboxes I need to create a new set of CSS
What I meant in my first post was having:
But, on a second though, looking at how CSS works I realizes it might not be feasible for this great CSS-only library. SCSS can offer ease of use (variables and mixins to easily create new themes, even without the namespace constraint or following it but using aliases to avoid repetition): so I guess using it resolves the issues I had. PS: the only direct advantage I can hold on is: If all checkboxes styles by this library have the Thanks for the answer. |
Thanks for explanation.
As you can see in About your point "When I need a new color for my checkboxes I need to create a new set of CSS" , no, you can create any number of color classes in a single file, like we did all colors in For example, if you use scss, you can use If you want to use scss in your theme class, you can import only I mean if you using sass, everything is very flexible. If not, you can just remove from main css file color classes, and add them in your theme files.. About having 2 classes, I do not see if that is critical. If you warry about jQuery selector, you can add second class, |
Could the library updated to use 2 CSS classes instead of one: one to say it's a checkbox with material design and the other to give it's color?
For example (where
u-colorTeal
only contains color-ing stuff):I see some advantages:
What do you think?
The text was updated successfully, but these errors were encountered: