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
In few places in my project I'm using "stretched link" - which is something I originally found in Bootstrap. I'm currently porting the project to Tailwind + Daisy and for that element I'm using suggestion provided in Tailwind's Github.
It was working fine on most of the elements where the link was just a text element but now I'm trying to get it working with .btn - and this is failing...
What happens: when hovering over the card, cursor changes to link coursor and browser shows the link in the bottom left, but when clicking it, nothing happens.
Thank you @pawelpbm
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?
4.7.2
Which browsers are you seeing the problem on?
Chrome
Reproduction URL
https://play.tailwindcss.com/nkymmKsw2I
Describe your issue
In few places in my project I'm using "stretched link" - which is something I originally found in Bootstrap. I'm currently porting the project to Tailwind + Daisy and for that element I'm using suggestion provided in Tailwind's Github.
It was working fine on most of the elements where the link was just a text element but now I'm trying to get it working with
.btn
- and this is failing...What happens: when hovering over the card, cursor changes to link coursor and browser shows the link in the bottom left, but when clicking it, nothing happens.
Minimal repro is here: https://play.tailwindcss.com/nkymmKsw2I
After quite a bit of messing with it I narrowed it down to
.btn
and specifically this part:When I add
active:hover:transform-none active:focus:transform-none
to thea
element all is working fine.I'm afraid I do not know HTML/CSS good enough to figure out if this is a bug or if I'm doing stuff wrong...
The text was updated successfully, but these errors were encountered: