junk: Scoped button CSS variables #5
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Context
Proof of concept for scoping of CSS variables i.e. not within a
:root { }block.The scoping demonstrated in this file provides very succinct and I would argue more readable code and results in far fewer variables. This works well when being consumed as a package. Further discovery work should be done to see how this could be optimised for theming.
Caveat
Scoped variables do not work well with CSS variable compiling using a Postcss plugin such as postcss-css-variables or postcss-custom-properties.
See below a summary of how CSS properties compile to hex values: