\n```",[2048,2049],{"name":1985,"color":1986},{"name":1988,"color":1989},3517,"How To Style NavigationMenu items","2025-03-14T13:01:49Z","https://github.com/nuxt/ui/issues/3517",0.6533827,{"description":2056,"labels":2057,"number":2065,"owner":1991,"repository":1992,"state":2066,"title":2067,"updated_at":2068,"url":2069,"score":2070},"### Environment\n\n- Operating System: Darwin\n- Node Version: v20.18.0\n- Nuxt Version: 3.14.1592\n- CLI Version: 3.16.0\n- Nitro Version: 2.10.4\n- Package Manager: pnpm@9.12.3\n- Builder: -\n- User Config: default\n- Runtime Modules: @nuxt/image@1.8.1, @nuxt/content@2.13.4, @nuxthq/studio@1.1.2, @nuxt/ui-pro@3.0.0-alpha.10, @nuxtjs/plausible@1.2.0, @nuxtjs/seo@2.0.2, @vueuse/nuxt@12.0.0\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.0.0.alpha10\n\n### Reproduction\n\nhttps://ui3.nuxt.dev/components/button#loading (example with `loading-auto`)\n\n### Description\n\nWhen using a `UIButton` component with an `@click` event, the cursor does not change to `cursor-pointer`, which may confuse users about the button's clickability.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2058,2061,2064],{"name":2059,"color":2060},"bug","d73a4a",{"name":2062,"color":2063},"duplicate","cfd3d7",{"name":1988,"color":1989},2940,"closed","`cursor-pointer` is missing on `UButton` with an `@click` event","2025-04-02T09:37:12Z","https://github.com/nuxt/ui/issues/2940",0.6224644,{"description":2072,"labels":2073,"number":2076,"owner":1991,"repository":1992,"state":2066,"title":2077,"updated_at":2078,"url":2079,"score":2080},"### Environment\n\n- Operating System: Windows_NT\n- Node Version: v22.11.0\n- Nuxt Version: 3.14.1592\n- CLI Version: 3.15.0\n- Nitro Version: -\n- Package Manager: pnpm@9.14.2\n- Builder: -\n- User Config: default\n- Runtime Modules: ../src/module, @nuxt/ui@3.0.0-alpha.9\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\n^3.0.0-alpha.9\n\n### Reproduction\n\nNormal Nuxt app setup as mentioned here https://ui3.nuxt.dev/getting-started/installation/nuxt\n- Use latest Nuxt app. \n- Add @tailwindcss 4 with vite and install this @nuxt/ui module and add it to Nuxt app. \n- Add @nuxt/ui import to tailwind css file\n\n### Description\n\n- Components such as UButton displays nicely\n- Components such as Accordion or Drawer fails. \n\nHere's a sample code used in `pages/index.vue` file\n\n```html\n\u003CUButton :ui=\"{ base: 'bg-primary-500' }\" class=\"inline-block\">UButton\u003C/UButton>\n\n \u003CUButton label=\"Show toast\" color=\"secondary\" variant=\"solid\" @click=\"showToast\" />\n\n \u003C!-- \u003CUAccordion :items=\"items\" /> -->\n\n \u003CUDrawer id=\"drawer\">\n \u003CUButton label=\"Open\" color=\"surface\" variant=\"solid\" />\n \u003Ctemplate #content>\n \u003CBaseUiPlaceholder class=\"h-48 m-4\" />\n \u003C/template>\n \u003C/UDrawer>\n```\n\nIf we use Accordion or Drawer (as mentioned in above code), we get 500 Error and app crashes. \n\n\n\nIf we comment out the Accordion and Drawer, no error comes, and app works nicely. \n\n\n\nSee: No error if we don't use the error-causing components. \n\n\n\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2074,2075],{"name":2059,"color":2060},{"name":1988,"color":1989},2769,"[v3] Error `$setup.useId is not a function` in Accordion, Drawer, etc.","2024-11-26T13:44:15Z","https://github.com/nuxt/ui/issues/2769",0.6302072,{"description":2082,"labels":2083,"number":2086,"owner":1991,"repository":1992,"state":2066,"title":2087,"updated_at":2088,"url":2089,"score":2090},"### Description\n\ni noticed that NUXT UI / NUXT UI PRO were refactored to use tailwind's new version 3 stuff + radix...\n\ni just went to the tailwind docs today and it looks like they just skipped right past their new version 3 and went to version 4...\n\nany ideas how this effects NUXT UI/PRO? \n\nMy undersanding is that version 3->4 means it was a semver breaking change?",[2084,2085],{"name":1985,"color":1986},{"name":1988,"color":1989},3167,"tailwind version 4..?","2025-01-24T10:17:32Z","https://github.com/nuxt/ui/issues/3167",0.633809,{"description":2092,"labels":2093,"number":2096,"owner":1991,"repository":1992,"state":2066,"title":2097,"updated_at":2098,"url":2099,"score":2100},"### Environment\n\n\n Operating System: Windows_NT\n Node Version: v20.18.0\n Nuxt Version: 3.13.2\n CLI Version: 3.14.0\n Nitro Version: 2.9.7\n Package Manager: pnpm@9.12.1\n Builder: -\n User Config: -\n Runtime Modules: -\n Build Modules: -\n\n\n### Version\n\nv3.0.0-alpha.6\n\n### Reproduction\n\nCannot use v3 on stackblitz so no repo.\n\n### Description\n\nIt looks like `onSelect?(e: Event): void` doesn't work, instead it is `select?(e: Event): void`. \nSpent a good amount of time until I figured it out. :')\nDocs problem only or something else?\n\nOnly tried nav and dropdown menus but this probably happens on all components that have onSelect:\n\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2094,2095],{"name":2059,"color":2060},{"name":1988,"color":1989},2392,"[NavigationMenu/DropdownMenu etc] 'onSelect' doesn't work, instead it is 'select' only","2024-10-16T09:55:28Z","https://github.com/nuxt/ui/issues/2392",0.63548934,["Reactive",2102],{},["Set"],["ShallowReactive",2105],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"kSt1mUPE282b8ltOr47vyNzs4-EDR6C7AQbg79IIbyM":-1},"/nuxt/nuxt.com/1533"]