-
When I have a setup like <div class="btm-nav">
<a href="/" class="active">
...
</a>
</div> it causes Tailwind/DaisyUI to produce CSS like this: .btm-nav > :where(.active) {
border-top-width: 2px;
--tw-bg-opacity: 1;
background-color: var(--fallback-b1, oklch(var(--b1) / var(--tw-bg-opacity)));
} which is great, but my framework already sets
Unfortunately, it's not turning out to be as simple as doing a[aria-current="page"] {
@apply active;
} in my Tailwind's input CSS file. Is it possible to get that It's not the end of the world if there's no solution here, as I am able to put the |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
Never mind, I just had to remove the [aria-current="page"] {
@apply active;
} works exactly as it should. 😅 |
Beta Was this translation helpful? Give feedback.
Never mind, I just had to remove the
a
from[aria-current="page"]
to get it to work; i.e.works exactly as it should. 😅