We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Rainbow Sprinkles currently doesn't accept values as an array when declaring CSS properties.
This could be useful when using the graceful degradation technique for legacy browser fallbacks, similar to what vanilla-extract has outlined here: https://vanilla-extract.style/documentation/styling/#fallback-styles.
const { className, style, otherProps } = rainbowSprinkles({ overflow: ['auto', 'overlay'], });
Other instances where it is useful to have this supported: https://stackoverflow.com/questions/44793453/how-do-i-add-a-top-and-bottom-shadow-while-scrolling-but-only-when-needed. This is where I landed in my investigation and this is the actual particular use case that I am solving for. Please suggest alternatives if any are known as a possible stop gap. Thank you.
The text was updated successfully, but these errors were encountered:
I think this is reasonable! PRs welcome.
Sorry, something went wrong.
No branches or pull requests
Problem Statement
Rainbow Sprinkles currently doesn't accept values as an array when declaring CSS properties.
This could be useful when using the graceful degradation technique for legacy browser fallbacks, similar to what vanilla-extract has outlined here: https://vanilla-extract.style/documentation/styling/#fallback-styles.
Proposed Solution
const { className, style, otherProps } = rainbowSprinkles({ overflow: ['auto', 'overlay'], });
Additional Context
Other instances where it is useful to have this supported:
https://stackoverflow.com/questions/44793453/how-do-i-add-a-top-and-bottom-shadow-while-scrolling-but-only-when-needed. This is where I landed in my investigation and this is the actual particular use case that I am solving for. Please suggest alternatives if any are known as a possible stop gap. Thank you.
The text was updated successfully, but these errors were encountered: