Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The idea is to add an "invisible" Button. It's just a square that has no background, borders etc. Useful for things like icon buttons, where you only see the icon and nothing else. Or maybe a list item that you can click on, or a button that is part of header.
But I'm not sure if it's the right way, because the selector to fight specificity is getting ugly (lots of class chaining). For example if you wanna customize that "glass button" while using the light theme, you'd have to select it like this:
I fear that people would just use
!important
everywhere, but that will cause more conflicts for them. Hmm.. My dream is to have just a single Montage class, no matter if it's a skin or a variation. So the skin would be "backed into"digit-Button
anddigit-Button--glass
could be used stand alone without being dependent ondigit-Button
. That would increase file size a bit (maybe not a too big concern). But maybe a bigger problem is authoring all the variations.. you would have a lot of duplicated styles that are hard to update. A solution could be a preprocessor that lets you extend CSS classes.. basically the same as we do with the "abstract" components.