\nAnd the rendered link element : \n\u003Cimg width=\"517\" height=\"208\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/fbf26569-fc21-461e-9184-8653d73e53a4\" />\n\n### Logs\n\n```shell-script\n\n```",[3023,3026],{"name":3024,"color":3025},"bug","d73a4a",{"name":3027,"color":3028},"triage","ffffff",4639,"nuxt","ui","open","NuxtUI Pro : PageCard's rendered link \u003Ca> is not accessible with keyboard (tabindex=\"-1\")","2025-08-01T07:51:55Z","https://github.com/nuxt/ui/issues/4639",0.7062666,{"description":3038,"labels":3039,"number":3045,"owner":3030,"repository":3031,"state":3032,"title":3046,"updated_at":3047,"url":3048,"score":3049},"### Environment\n\n- Operating System: `Darwin`\n- Node Version: `v24.3.0`\n- Nuxt Version: `4.0.0-rc.0`\n- CLI Version: `3.25.1`\n- Nitro Version: `2.11.13`\n- Package Manager: `pnpm@10.13.1`\n- Builder: `-`\n- User Config: `modules`, `devtools`, `css`, `compatibilityDate`, `eslint`, `storybook`\n- Runtime Modules: `@nuxt/eslint@1.5.2`, `@nuxt/image@1.10.0`, `@nuxt/scripts@0.11.9`, `@nuxt/test-utils@3.19.2`, `@nuxt/ui@3.2.0`, `@nuxthub/core@0.9.0`, `@nuxtjs/storybook@8.4.2-29190898.ba4cb15`, `@vueuse/nuxt@13.5.0`\n- Build Modules: `-`\n\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt but I guess it'll affect both versions.\n\n### Version\n\nv4.0.0-rc.0\n\n### Reproduction\n\nhttps://codesandbox.io/p/devbox/nuxt-ui-css-cascade-layers-not-working-forked-lw7yyg?workspaceId=ws_KLCsiXAt6fXZg7LEhmgRum\n\n### Description\n\n```css\n@import \"tailwindcss\" layer(tailwindcss);\n@import \"@nuxt/ui\" layer(tailwindcss);\n```\n\nWhile Tailwind allows you to import its styles into its own css cascade layer, this module does not.\n\n\u003Cimg width=\"287\" height=\"242\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/7ce091cb-106b-4913-9416-03ce4f02218f\" />\n\nFrom what I understand, according to the error logged, the issue is caused by the resulting css tree having nested `@source` declarations.\n\n### Additional context\n\nI'm working on migrating an existing website that was built using Bootstrap (lol) and I'd like to use layers to ensure the newer css gets a higher priority than the old one.\n\nUsing `@import \"tailwindcss\" layer(tailwindcss);` results in all the tailwind stuff being scoped to the `tailwindcss` layer (eg. `tailwindcss.theme`, `tailwindcss.base`…).\n\nHowever, when I try to do the same for `@import \"@nuxt/ui\"` I get the previously mentioned error.\n\nI've tried using both the same and a different layer name than the one I use for tailwind but I still get the error.\n\n### Logs\n\n```shell-script\nERROR Pre-transform error: @source cannot be nested. 12:42:31 PM\n Plugin: @tailwindcss/vite:generate:serve\n File: /project/workspace/app/assets/css/main.css\n```",[3040,3041,3044],{"name":3024,"color":3025},{"name":3042,"color":3043},"v3","49DCB8",{"name":3027,"color":3028},4503,"`@import \"@nuxt/ui\" layer(layer-name);` not working","2025-07-11T13:35:06Z","https://github.com/nuxt/ui/issues/4503",0.7505191,{"description":3051,"labels":3052,"number":3056,"owner":3030,"repository":3031,"state":3057,"title":3058,"updated_at":3059,"url":3060,"score":3061},"### Environment\n\n- Operating System: Linux\n- Node Version: v20.12.0\n- Nuxt Version: 3.17.3\n- CLI Version: 3.25.1\n- Nitro Version: 2.11.12\n- Package Manager: pnpm@8.15.6\n- Builder: -\n- User Config: modules, devtools, compatibilityDate, future, css\n- Runtime Modules: @nuxt/ui@3.1.3\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.1.3\n\n### Reproduction\n\nhttps://codesandbox.io/p/devbox/admiring-firefly-pw9d9p\n\n### Description\n\nUsing a vertical orientation along with `type=\"single\"`, if there is only one level of children, works great. Clicking on another item to select causes the current item to collapse and new one expands.\n\nWhen you have more nested levels though, clicking on child items bubbles up and closes all parents up to top.\n\nI've added two `UNavigationMenu` items, the first one has one level and works fine, the seconds one is where the issue is demonstrated.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3053,3054,3055],{"name":3024,"color":3025},{"name":3042,"color":3043},{"name":3027,"color":3028},4329,"closed","`UNavigationMenu` nested accordions close all levels when `type=\"single\"`","2025-06-17T08:49:09Z","https://github.com/nuxt/ui/issues/4329",0.73562384,{"description":3063,"labels":3064,"number":3073,"owner":3030,"repository":3031,"state":3057,"title":3074,"updated_at":3075,"url":3076,"score":3077},"### Environment\n\nNuxt v3.1.0\n\n### Is this bug related to Nuxt or Vue?\n\nVue\n\n### Version\n\nv3.1.0\n\n### Reproduction\n\nNot sure how to share out an intertia/laravel app.\n\n### Description\n\nI was able to move forward with the Intertia JS improvements with Links, however... I'm trying to use the Header component and the toggle isn't working. I can see in the header.vue component that useRoute is being used, and it' causing the app to not open and close the menu correctly.\n\nI can see it opening for a flash, then closed. I tried doing something manually with watching for the update:open, but I can see this is not the solution... I immediately had issues closing and losing the link focus trap when the menu appears.\n\nI'm using Nuxt UI Pro v3.1.0 - I'm about to purchase a liceense so I can confirm this works with SSR enabled, but I'm blocked with this basic implemention.\n\n```\n \u003CUApp>\n \u003CUHeader mode=\"drawer\">\n \u003Ctemplate #title>\n \u003CApplicationLogo class=\"h-6 w-auto\" />\n \u003C/template>\n\n \u003CUNavigationMenu :items=\"items\" />\n\n \u003Ctemplate #right>\n \u003CUColorModeSelect />\n \u003C/template>\n\n \u003Ctemplate #body>\n \u003CUNavigationMenu :items=\"items\" orientation=\"vertical\" class=\"-mx-2.5\" />\n \u003C/template>\n \u003C/UHeader>\n\u003C/UApp>\n```\n\nI can see this will be a problem with more components...\n\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3065,3066,3067,3070],{"name":3024,"color":3025},{"name":3042,"color":3043},{"name":3068,"color":3069},"@nuxt/ui-pro","5BD3CB",{"name":3071,"color":3072},"inertia","b60205",3990,"Header toogle menu not working in an Intertia app (useRoute still being used)","2025-05-04T15:36:46Z","https://github.com/nuxt/ui/issues/3990",0.74313194,{"description":3079,"labels":3080,"number":3084,"owner":3030,"repository":3030,"state":3057,"title":3085,"updated_at":3086,"url":3087,"score":3088},"### Environment\n\n```\r\n- Operating System: Linux\r\n- Node Version: v18.19.1\r\n- Nuxt Version: 3.12.3\r\n- CLI Version: 3.12.0\r\n- Nitro Version: 2.9.7\r\n- Package Manager: bun@1.1.20\r\n- Builder: -\r\n- User Config: alias, app, components, css, devtools, hooks, i18n, imports, modules, pwa, runtimeConfig, shadcn, srcDir, ssr, supabase, tailwindcss, typescript, vite, vue, compatibilityDate\r\n- Runtime Modules: @pinia/nuxt@0.5.1, @vite-pwa/nuxt@0.9.1, @nuxtjs/i18n@8.3.1, @nuxtjs/supabase@1.2.2, @nuxtjs/tailwindcss@6.12.0, shadcn-nuxt@0.10.4\r\n- Build Modules: -\r\n```\n\n### Reproduction\n\nhttps://stackblitz.com/edit/github-pnptkr?file=app.vue\n\n### Describe the bug\n\nAfter upgrade to 3.12.3 navigation stops to work on pages that use navigation guards from Nuxt.\r\n\r\nBy default no return in `onBeforeRouteLeave` should work but after adding explicit `return true` below message is printed in the console. \r\n\r\n\r\nSo this makes it clear that as a workaround I need to add all parameters and call `next()` explicitly.\r\n\r\nI see in tsconfig that latest version has changed how `#vue-router` is imported:\r\n\r\n\r\nIt does not seem to be related from the issue perspective but maybe above finding might also help with solving other router issues, since warnings might not be shown in default usage:\r\nhttps://github.com/nuxt/nuxt/issues/28086\r\nhttps://github.com/nuxt/nuxt/issues/28122\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[3081],{"name":3082,"color":3083},"pending triage","E99695",28141,"Navigation guards like onBeforeRouteLeave might prevent all navigation after upgrade to 3.12.3","2024-07-13T17:01:34Z","https://github.com/nuxt/nuxt/issues/28141",0.74338955,{"labels":3090,"number":3098,"owner":3030,"repository":3030,"state":3057,"title":3099,"updated_at":3100,"url":3101,"score":3102},[3091,3094,3095],{"name":3092,"color":3093},"3.x","29bc7f",{"name":3024,"color":3025},{"name":3096,"color":3097},"upstream","E8A36D",13893,"Cannot access 'hello$1' before initialization","2024-06-17T17:48:06Z","https://github.com/nuxt/nuxt/issues/13893",0.7436295,{"description":3104,"labels":3105,"number":3110,"owner":3030,"repository":3030,"state":3057,"title":3111,"updated_at":3112,"url":3113,"score":3114},"### Environment\n\n````\n------------------------------\n- Operating System: Linux (Ubuntu 20.04 LTS)\n- Node Version: v20.12.2\n- Nuxt Version: 3.14.159\n- CLI Version: 3.15.0\n- Nitro Version: -\n- Package Manager: pnpm@8.1.0\n- Builder: -\n- User Config: default\n- Runtime Modules: @nuxtjs/tailwindcss@6.12.2, @vueuse/nuxt@11.2.0, @pinia/nuxt@0.7.0\n- Build Modules: -\n------------------------------\n````\n\n### Reproduction\n\nhttps://stackblitz.com/~/github.com/martinszeltins/nuxt-3-14-pinia-issue?file=app.vue\n\n### Describe the bug\n\nSince Nuxt `3.14` the Pinia tab in devtools seems to be broken showing `No Data` while this was working in `3.13`\n\nPlease see the reproduction.\n\nScreenshot:\n\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3106,3107],{"name":3082,"color":3083},{"name":3108,"color":3109},"possible regression","B90A42",29944,"Pinia tab is broken in `3.14`","2024-11-17T19:36:39Z","https://github.com/nuxt/nuxt/issues/29944",0.7462724,{"description":3116,"labels":3117,"number":3123,"owner":3030,"repository":3031,"state":3057,"title":3124,"updated_at":3125,"url":3126,"score":3127},"### Environment\n\n- Operating System: `Darwin`\n- Node Version: `v23.10.0`\n- Nuxt Version: `3.17.0`\n- CLI Version: `3.25.0`\n- Nitro Version: `2.11.10`\n- Package Manager: `pnpm@10.10.0`\n- Builder: `-`\n- User Config: `-`\n- Runtime Modules: `-`\n- Build Modules: `-`\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.1.0\n\n### Reproduction\n\nAny use of tabs slots\n\n### Description\n\nAfter upgrading all dependencies to the latest version and keeping NuxtUI v3.0.2 everything is ok but when in addition to other dependencies I also upgrade NuxtUI to the latest version v3.1.0 then TS errors appear as in the attached screen shot so I guess again a step backwards from the recent fixes with slots ;p\n\n\n\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3118,3119,3122],{"name":3024,"color":3025},{"name":3120,"color":3121},"duplicate","cfd3d7",{"name":3042,"color":3043},4005,"Tab slots types error","2025-04-28T10:54:47Z","https://github.com/nuxt/ui/issues/4005",0.74713933,{"description":3129,"labels":3130,"number":3135,"owner":3030,"repository":3030,"state":3057,"title":3136,"updated_at":3137,"url":3138,"score":3139},"### Environment\n\n------------------------------\n- Operating System: Windows_NT\n- Node Version: v20.17.0\n- Nuxt Version: \n 3.14.1592 \n- CLI Version: \n 3.16.0\n- Nitro Version: \n 2.10.4\n- Package Manager:\n yarn@1.22.19 \n- Builder: \n -\n- User Config: \n default\n- Runtime Modules:\n @nuxt/ui@2.20.0,\n @pinia/nuxt@0.9.0\n, pinia-plugin-per\nsistedstate/nuxt, \ndayjs-nuxt@2.1.11,\n @nuxtjs/device@3.\n2.4, @vueuse/nuxt@\n12.0.0, @element-p\nlus/nuxt@1.1.0, nu\nxt-echarts@0.2.4, \n@formkit/auto-anim\nate/nuxt@0.8.2, @tresjs/nuxt@3.0.7 \n\n\n### Reproduction\n\n\nSwitching him seems to sometimes result in multiple pages, overlapping the pages from two routes. But it's not 100% likely to happen.\n\n\n\n### Describe the bug\n\n\nSwitching him seems to sometimes result in multiple pages, overlapping the pages from two routes. But it's not 100% likely to happen.\n\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3131,3132],{"name":3082,"color":3083},{"name":3133,"color":3134},"needs reproduction","FBCA04",30388,"Nested routing sometimes has bugs","2025-03-24T23:17:41Z","https://github.com/nuxt/nuxt/issues/30388",0.7473712,{"description":3141,"labels":3142,"number":3151,"owner":3030,"repository":3031,"state":3057,"title":3152,"updated_at":3153,"url":3154,"score":3155},"### Environment\n\n- Operating System: `Windows 11`\n- Browser: `Chrome 131`\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt UI\n\n### Version\n\nv2.20.0, 3.0.0-alpha-x\n\n### Reproduction\n\n[Tabs ](https://ui.nuxt.com/components/tabs) and [Input#disabled](https://ui.nuxt.com/components/input#disabled) sections of ui.nuxt.com, as well as pretty much every other component that has a \"Disabled\" state, demonstrate the issue\n\n### Description\n\nThe current styling for `disabled` state of different components in Nuxt UI has a very subtle visual distinction from the enabled state. On a monitor with good sRGB calibration (Gigabyte M32U - IPS, 4K, sRGB mode), the grayed-out appearance of the `disabled` state in almost every Nuxt UI component (as shown on the [ui.nuxt.com/components](https://ui.nuxt.com/components)) is almost indistinguishable from the non-disabled state.\n\n**Issue:**\n- Disabled elements do not provide a clear visual cue, making it hard for users to differentiate their state at a glance.\n- This affects usability and accessibility, especially for users with mild visual impairments or varying screen settings.\n\n**Suggestion:**\n\nConsider increasing contrast differences or adding clearer indicators (e.g., opacity) to improve visual accessibility for disabled elements.\n\n**Example:**\n[Tabs](https://ui.nuxt.com/components/tabs) and [Input#disabled](https://ui.nuxt.com/components/input#disabled) sections of ui.nuxt.com, as well as pretty much every other component that has a \"Disabled\" state, demonstrate the issue.\n\n**Video** (may look different on your monitor):\nNuxt UI `2.20.0`:\n\n\nhttps://github.com/user-attachments/assets/81eea3ee-1c74-4036-9fe9-55b18cb16851\n\n\nNuxt UI `3.0.0-alpha-x`:\n\n\nhttps://github.com/user-attachments/assets/9018589e-98fb-46d1-97e5-623fae98727e\n\n\n**Photos** of how it looks like on the mentioned monitor:\n\n\u003Cimg src=\"https://github.com/user-attachments/assets/97736e43-fe88-428a-b3b2-67fcbe9b37dc\" width=\"400\"/>\n\n\u003Cimg src=\"https://github.com/user-attachments/assets/6caf4ee6-0cb9-4c7e-9bc7-07e320248b8e\" width=\"400\"/>\n\n\u003Cimg src=\"https://github.com/user-attachments/assets/b64d9960-4877-4fc4-b016-92ce8c4cf393\" width=\"400\"/>\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3143,3144,3145,3146,3149],{"name":3024,"color":3025},{"name":3042,"color":3043},{"name":3027,"color":3028},{"name":3147,"color":3148},"closed-by-bot","ededed",{"name":3150,"color":3148},"stale",2995,"Improve disabled state visibility for Tabs and other components","2025-06-18T09:02:44Z","https://github.com/nuxt/ui/issues/2995",0.7476911,["Reactive",3157],{},["Set"],["ShallowReactive",3160],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$f6QPYuL9h6bfrRPuXf2wmhuU-Q7fVEHBlTXMw_w9mbWE":-1},"/nuxt/ui/1428"]