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
Probably super edge-case, sorry in advance 😄. Reproduction repo is linked, could not create a stackblitz because it seems tailwind v4 does not work with stackblitz.
The issue is that if you use a <UChip> to wrap your <UButton> that acts as a trigger for <UModal> or <UDrawer> (probably also for other components?), the aria-* values are not applied properly.
So usually, the trigger button HTML should look like this:
@DrxcoDev Thanks for your comment, unfortunately I think some parts of it got trimmed away, that happens when you write a component name but without backticks
Environment
Darwin
v20.14.0
3.13.2
3.15.0
2.9.7
[email protected]
-
default
@nuxt/[email protected]
-
Version
3.0.0-alpha.7
Reproduction
https://github.com/madebyfabian/nuxt-ui3-drawer-chip-button-reprod
Description
Probably super edge-case, sorry in advance 😄. Reproduction repo is linked, could not create a stackblitz because it seems tailwind v4 does not work with stackblitz.
The issue is that if you use a
<UChip>
to wrap your<UButton>
that acts as a trigger for<UModal>
or<UDrawer>
(probably also for other components?), the aria-* values are not applied properly.So usually, the trigger button HTML should look like this:
But when wrapped with a Chip (see the
app.vue
in the reproduction repo), it looks like this:so the aria-* attributes are applied to the parent
<div>
node and not the<button>
, which causes Lighthouse to complain (thats why I noticed).Not sure if that's a Nuxt UI specific issue or it's more in the underlying Vue Radix.
Additional context
No response
Logs
No response
The text was updated successfully, but these errors were encountered: