Replies: 1 comment
-
There are two ways to resolve this: 1 - Using backdropFilter auto and setting the individual backdrop properties const overlayStyle = css({
backgroundColor: "overlayBackground",
backdropFilter: "auto",
backdropBlur: "overlay"
}) 2 - Use the token reference syntax const overlayStyle2 = css({
backgroundColor: "overlayBackground",
backdropFilter: "blur({blurs.overlay})",
}) |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi team
We’ve been building a system around Panda and Radix Theme and loving the structured token approach — especially the clarity around colours. However, we’ve hit a wall when trying to apply non-colour tokens (e.g. blurs, opacities, spacing, etc.) in actual style declarations — and I’m wondering if we’re doing something wrong, or if this is a current limitation.
What We Tried
We defined tokens like this:
We then attempted to use them in css() style objects:
What We Observed
Questions
Why This Matters
We’re building a token-governed system under a styling doctrine that avoids inline values unless strictly necessary. Colour tokens work great — but consistency falls apart when blur, opacity or sizing tokens fail silently. We’d love to know if this is a usage issue or a compiler limitation.
Thanks for the fantastic work — really hoping we’re just missing something obvious!
Beta Was this translation helpful? Give feedback.
All reactions