You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While playing around with daisyUI I've noticed that the daisyUI Button is not taking --fallback-p CSS token as the the first var() option for background color, due to implementation with token called --btn-color and it always expects --falback-p or --p to be in oklch format
Thank you @icukovic
for reporting issues. It helps daisyUI a lot 💚
I'll be working on issues one by one. I will help with this one as soon as a I
find a solution.
In the meantime providing more details and reproduction links would be
helpful.
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: