\n \u003C/div>\n\u003C/template>\n```\n\n### Logs\n\n```shell-script\n\n```",[2923,2924],{"name":2896,"color":2897},{"name":2860,"color":2861},2755,"Veritcal NavigationMenu - `defaultOpen` doesn't work","2024-11-26T10:29:27Z","https://github.com/nuxt/ui/issues/2755",0.625699,{"description":2931,"labels":2932,"number":2936,"owner":2863,"repository":2864,"state":2905,"title":2937,"updated_at":2938,"url":2939,"score":2940},"### Environment\n\n- Operating System: Linux\n- Node Version: v20.17.0\n- Nuxt Version: ^3.13.0\n- CLI Version: 3.14.0\n- Package Manager: bun\n- Nuxt Ui: ^3.0.0-alpha.6\n\n\n### Version\n\n3.0.0-alpha.6\n\n### Reproduction\n\n1. Clone https://github.com/malte-baumann/z-index\n2. bun dev (or similar)\n3. Open modal / slideover / drawer\n4. Click on Select / DropdownMenu / InputMenu\n5. See what you don't see\n\n### Description\n\nI opend #2404 recently and noticed some more z-index problems. \nAt least these Components: \n- Select\n- DropdownMenu\n- InputMenu \ndon't have high enough z-indexes inside a Drawer / Modal / Slideover to show their popover contents. \n\n\n\n### Additional context\n\n\n\n\n### Logs\n\n_No response_",[2933,2934,2935],{"name":2896,"color":2897},{"name":2899,"color":2900},{"name":2860,"color":2861},2421,"Z-Indexes inside Modal / Slideover / Drawer","2024-10-21T10:15:59Z","https://github.com/nuxt/ui/issues/2421",0.62770957,{"description":2942,"labels":2943,"number":2947,"owner":2863,"repository":2864,"state":2905,"title":2948,"updated_at":2949,"url":2950,"score":2951},"### 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```",[2944,2945,2946],{"name":2896,"color":2897},{"name":2899,"color":2900},{"name":2860,"color":2861},2940,"`cursor-pointer` is missing on `UButton` with an `@click` event","2025-04-02T09:37:12Z","https://github.com/nuxt/ui/issues/2940",0.63340425,{"description":2953,"labels":2954,"number":2957,"owner":2863,"repository":2864,"state":2905,"title":2958,"updated_at":2959,"url":2960,"score":2961},"### 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?",[2955,2956],{"name":2857,"color":2858},{"name":2860,"color":2861},3167,"tailwind version 4..?","2025-01-24T10:17:32Z","https://github.com/nuxt/ui/issues/3167",0.63553894,{"description":2963,"labels":2964,"number":2967,"owner":2863,"repository":2864,"state":2905,"title":2968,"updated_at":2969,"url":2970,"score":2971},"### Environment\n\n- Operating System: Linux\n- Node Version: v23.3.0\n- Nuxt Version: 3.15.1\n- CLI Version: 3.18.2\n- Nitro Version: 2.10.4\n- Package Manager: pnpm@9.13.2\n- Builder: -\n- User Config: devtools, modules, css, future, compatibilityDate\n- Runtime Modules: @nuxt/ui@3.0.0-alpha.9, @nuxt/eslint@0.7.4\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\n3.15.1\n\n### Reproduction\n\nhttps://github.com/fl5brkv/nuxt-issue\n\n### Description\n\nI installed nuxt ui 3 from the official nuxt ui starter, just wanted to try the calendar, but it doesnt work. Throwing me warnings in console.log.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n[Vue warn]: Failed to resolve component: UCalendar\nIf this is a native custom element, make sure to exclude it from component resolution via compilerOptions.isCustomElement. \n at \u003CIndex onVnodeUnmounted=fn\u003ConVnodeUnmounted> ref=Ref\u003C undefined > > \n at \u003CAnonymous key=\"/\" vnode= Object route= Object ... > \n at \u003CRouterView name=undefined route=undefined > \n at \u003CNuxtPage > \n at \u003CToastProvider swipe-direction=\"right\" duration=5000 > \n at \u003CToaster key=0 > \n at \u003CTooltipProvider > \n at \u003CConfigProvider use-id=fn\u003Cuse-id> dir=\"ltr\" > \n at \u003CApp > \n at \u003CApp key=4 > \n at \u003CNuxtRoot>\n\nruntime-core.esm-bundler.js?v=b66559bc:50 [Vue warn]: Hydration node mismatch:\n- rendered on server: \u003C!----> \n- expected on client: UCalendar \n at \u003CIndex onVnodeUnmounted=fn\u003ConVnodeUnmounted> ref=Ref\u003C undefined > > \n at \u003CAnonymous key=\"/\" vnode= Object route= Object ... > \n at \u003CRouterView name=undefined route=undefined > \n at \u003CNuxtPage > \n at \u003CToastProvider swipe-direction=\"right\" duration=5000 > \n at \u003CToaster key=0 > \n at \u003CTooltipProvider > \n at \u003CConfigProvider use-id=fn\u003Cuse-id> dir=\"ltr\" > \n at \u003CApp > \n at \u003CApp key=4 > \n at \u003CNuxtRoot>\n```",[2965,2966],{"name":2896,"color":2897},{"name":2860,"color":2861},3044,"\u003CUCalendar /> isn't rendering","2025-01-08T09:24:13Z","https://github.com/nuxt/ui/issues/3044",0.63715494,["Reactive",2973],{},["Set"],["ShallowReactive",2976],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fjY1JgsG990krlTZhV4z2m9jEdnohB54lKqqHSKEJh5c":-1},"/nuxt/ui/3900"]