-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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: Component states are not working with Modifier #3652
Comments
Thank you @PruthviPraj00
for reporting issues. It helps daisyUI a lot 💚
|
Hello @saadeghi, I raised this issue in tailwindcss, and they responded, you can take a look, hope this helps |
Will be fixed soon in the next patch version. |
Hello @saadeghi, Did you find any solution or any workaround for this? |
The bug doesn't happen only with |
Reproduction URL (Required)
https://play.tailwindcss.com/wWndQ9FxeZ
https://play.tailwindcss.com/L2yalFmJcY
What version of daisyUI are you using?
V5.0.2
Which browsers are you seeing the problem on?
All browsers
Describe your issue
Hii @pouya 🌼,
I’m encountering an issue with DaisyUI V5. Component states like btn-active and menu-active no longer work with the Tailwind modifiers. This functionality worked fine in V4, but it seems broken in the current version.
To reproduce the issue, try the following code in the DaisyUI playground. Test it in both V5 and V4 to compare:
I think the issue is from tailwindcss
https://play.tailwindcss.com/V9PpCvsjHl
The text was updated successfully, but these errors were encountered: