-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
bug: btn doesn't accept --fallback
tokens as first option.
#2975
Comments
Thank you @icukovic
for reporting issues. It helps daisyUI a lot 💚
|
Also I understand that this |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What version of daisyUI are you using?
v4.10.1
Which browsers are you seeing the problem on?
All browsers
Reproduction URL
https://play.tailwindcss.com/XuToYOqkWo
Describe your issue
While playing around with daisyUI I've noticed that the daisyUI Button is not taking
--fallback-p
CSS token as the the firstvar()
option for background color, due to implementation with token called--btn-color
and it always expects--falback-p
or--p
to be in oklch formatdaisyUI src/component/styled/button.css as of today for browsers that support oklch generates:
while src/components/styled/badge.css for comparison always accepts
--fallback
tokens as first and they can be in any type value.The text was updated successfully, but these errors were encountered: