\n```\n\n### Will results something like this\n```html\n\u003Cdiv class=\"... root-test base-test\">\n ...\n \u003Cinput class=\"...\" />\n\u003C/div>\n```\n\n### Description\n\nWhen applying themes in `app.config.ts`, both **UInputTags** and **UInputMenu (multiple)** share the same weird behaviour compared with other components, where the class applied to `base` part of the component are applied to `root` part of the component.\n\n### Expected Behaviour\nThe applied class on `base` should be applied to the `\u003Cinput />`, not the `root` part of the component which is the outer `\u003Cdiv />` just like other input components such as **UInput**, **UInputNumber**, or **UTextarea**.\n\nCorrect me if I'm wrong if this are intended, thank you!\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3035,3038,3039],{"name":3036,"color":3037},"bug","d73a4a",{"name":3022,"color":3023},{"name":3040,"color":3041},"triage","ffffff",4530,"[UInputTags, UInputMenu] Theming behaviour issues","2025-07-15T17:50:02Z","https://github.com/nuxt/ui/issues/4530",0.7190608,{"description":3048,"labels":3049,"number":3053,"owner":3025,"repository":3026,"state":3027,"title":3054,"updated_at":3055,"url":3056,"score":3057},"### Environment\n\n- Operating System: Windows_NT\n- Node Version: v22.12.0\n- Nuxt Version: 3.17.4\n- CLI Version: 3.25.1\n- Nitro Version: 2.11.12\n- Package Manager: npm@10.9.0\n- User Config: compatibilityDate, devtools, ssr, future, app, css, modules, build, vite, eslint, i18n, runtimeConfig, experimental, imports\n- Runtime Modules: @nuxt/eslint@1.4.1, @nuxt/test-utils@3.19.1, @nuxt/ui@3.2.0, @nuxtjs/i18n@9.5.5\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.2.0\n\n### Reproduction\n\nhttps://codesandbox.io/p/devbox/nuxt-ui3-n3sxks\n\n### Description\n\nThe UNavigationMenu component doesn't have built-in support for generating localized routes when using @nuxtjs/i18n. When using locale prefixes (e.g., /en/dashboard, /ar/dashboard), the navigation items don't automatically adapt to the current locale.\n\n### Expected behavior:\nThe component should automatically handle locale prefixes when @nuxtjs/i18n is configured, similar to how \u003CNuxtLink> works with localePath().\n\n### Proposed solution:\nAuto-detect @nuxtjs/i18n configuration\nApply localePath() internally to to props\nAdd optional localized prop for explicit control\nMaintain backward compatibility\n\nThis would eliminate boilerplate code and improve DX for internationalized applications using Nuxt UI navigation components.\n\n\n### Additional context\n\n**Current Workaround Required:**\n```vue\n\u003Cscript setup>\nconst { locale } = useI18n()\n\n// Manual helper function needed\nconst getLocalizedRoute = (path) => {\n if (locale.value === 'ar') {\n return `/example/ar${path}`\n }\n return `/example${path}`\n}\n\nconst sidebarItems = computed(() => [\n [{\n label: 'Dashboard',\n icon: 'i-lucide-home',\n to: getLocalizedRoute('/dashboard/'), // Manual localization\n }]\n])\n\u003C/script>\n```\n\n### Logs\n\n```shell-script\n\n```",[3050,3051,3052],{"name":3036,"color":3037},{"name":3022,"color":3023},{"name":3040,"color":3041},4465,"UNavigationMenu lacks built-in support for localized routes (i18n)","2025-07-06T14:40:52Z","https://github.com/nuxt/ui/issues/4465",0.720105,{"description":3059,"labels":3060,"number":3064,"owner":3025,"repository":3026,"state":3065,"title":3066,"updated_at":3067,"url":3068,"score":3069},"### 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```",[3061,3062,3063],{"name":3036,"color":3037},{"name":3022,"color":3023},{"name":3040,"color":3041},4329,"closed","`UNavigationMenu` nested accordions close all levels when `type=\"single\"`","2025-06-17T08:49:09Z","https://github.com/nuxt/ui/issues/4329",0.66711974,{"description":3071,"labels":3072,"number":3075,"owner":3025,"repository":3026,"state":3065,"title":3076,"updated_at":3077,"url":3078,"score":3079},"### Environment\n\n- Operating System: Darwin\n- Node Version: v20.10.0\n- Nuxt Version: 3.15.4\n- CLI Version: 3.21.1\n- Nitro Version: 2.10.4\n- Package Manager: pnpm@9.15.0\n- Builder: -\n- User Config: compatibilityDate, future, devtools, modules, css\n- Runtime Modules: @nuxt/ui-pro@3.0.0-alpha.12, @nuxt/content@3.1.0\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.0.0-alpha.12\n\n### Reproduction\n\n```vue\n\u003Cscript setup>\nconst links = ref([\n {\n label: 'Components',\n to: '/components',\n active: route.path.startsWith('/components'),\n children: [\n {\n label: 'Sections',\n to: '/components/sections',\n icon: 'i-lucide-lightbulb',\n description:\n 'Sections are used to create a layout for your components.',\n active: route.path.startsWith('/components/sections')\n },\n {\n label: 'Snippets',\n to: '/components/snippets',\n icon: 'i-lucide-lightbulb',\n description:\n 'Snippets are used to create a layout for your components.',\n active: route.path.startsWith('/components/snippets')\n }\n ]\n }\n]);\n\u003C/script>\n\n\u003Ctemplate>\n \u003CUHeader>\n \u003CUNavigationMenu :items=\"links\" />\n \u003C/UHeader>\n\u003C/template>\n```\n\n### Description\n\nThe width of the menu depends on the amount of items it contains. When you have to few items, the width will be to small for the horizontal dropdown.\n\nNormally a dropdown is not related to the width of the menu, but in case of this animation I'm not sure enough to say how that could be fixed if the menu was not the relative parent.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3073,3074],{"name":3036,"color":3037},{"name":3022,"color":3023},3268,"`UNavigationMenu` dropdown has wrong relative parent","2025-05-23T13:02:31Z","https://github.com/nuxt/ui/issues/3268",0.6681108,{"description":3081,"labels":3082,"number":3086,"owner":3025,"repository":3026,"state":3065,"title":3087,"updated_at":3088,"url":3089,"score":3090},"### Environment\n\n- Nuxt 3.16.2 with Nitro 2.11.9\n- NuxtUI 3.1.1\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\n3.1.1\n\n### Reproduction\n\nhttps://codesandbox.io/p/devbox/quirky-wood-lnhsf5\n\n### Description\n\nWhen UNavigationMenu is vertical it's impossible to trigger navigation on root elements\neven if you specify `type: 'link', onselect: () => navigateTo('/test'), `\n\n### Additional context\n\nThe only workaround I have found is to do\n```\n\u003Ctemplate #item-label=\"{ item }\">\n \u003CNuxtLink :to=\"item.to\">{{ item.label }}\u003C/NuxtLink>\n\u003C/template>\n```",[3083,3084,3085],{"name":3036,"color":3037},{"name":3022,"color":3023},{"name":3040,"color":3041},4115,"UNavigationMenu vertical not triggering route \"to\" on root elements","2025-05-10T11:18:54Z","https://github.com/nuxt/ui/issues/4115",0.67772937,{"description":3092,"labels":3093,"number":3099,"owner":3025,"repository":3026,"state":3065,"title":3100,"updated_at":3101,"url":3102,"score":3103},"### Environment\n\n- Operating System: Darwin\n- Node Version: v20.11.1\n- Nuxt Version: 3.16.2\n- CLI Version: 3.25.1\n- Nitro Version: 2.11.12\n- Package Manager: npm@10.2.4\n- Builder: -\n- User Config: css, compatibilityDate, devtools, future, modules, runtimeConfig, ssr, typescript\n- Runtime Modules: @nuxt/eslint@1.4.0, @nuxt/fonts@0.11.4, @nuxt/ui-pro@3.1.2, @pinia/nuxt@0.5.5, @vueuse/nuxt@10.11.1, nuxt-auth-utils@0.5.20, nuxt-authorization@0.3.4\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.1.2\n\n### Reproduction\n\nJust use the code of https://github.com/nuxt-ui-pro/dashboard/blob/main/app/pages/settings.vue and add a child to one of the links used for the UNavigationMenu. Like :\n````\n{\n label: \"General\",\n icon: \"i-lucide-user\",\n to: \"/settings\",\n children: [\n {\n label: \"Hello\",\n icon: \"i-lucide-book-open\",\n },\n ],\n exact: true,\n },\n````\n\n### Description\n\nIt seems wrapping the UNavigationMenu component in UDashboardToolbar will cause the UNavigationMenu's links children dropdown to not appear or be hidden.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3094,3095,3096],{"name":3036,"color":3037},{"name":3022,"color":3023},{"name":3097,"color":3098},"nuxt/ui-pro","00dc82",4177,"UNavigationMenu item children not visible when wrapped in UDashboardToolbar","2025-05-23T12:23:17Z","https://github.com/nuxt/ui/issues/4177",0.682779,{"description":3105,"labels":3106,"number":3115,"owner":3025,"repository":3026,"state":3065,"title":3116,"updated_at":3117,"url":3118,"score":3119},"### Environment\n\n- Operating System: Darwin\n- Node Version: v23.3.0\n- Nuxt Version: 3.16.1\n- CLI Version: 3.23.1\n- Nitro Version: 2.11.7\n- Package Manager: pnpm@9.9.0\n- Builder: -\n- User Config: compatibilityDate, css, devtools, modules, colorMode, runtimeConfig, ui, app\n- Runtime Modules: @nuxt/ui@3.0.1, @nuxtjs/device@3.2.4\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.0.1\n\n### Reproduction\n\nhttps://codesandbox.io/p/devbox/modest-euclid-j92wtc\n\n### Description\n\nThe v-model does not open the tab of the navigation bar if this is not a \"parent of children\" type of tab. It's confusing because there is no more \"isActive\" items status since the v3.\n\n### Additional context\n\n(it's my first time creating an issue, maybe I've done some things wrong during creation)\n\n### Logs\n\n```shell-script\n\n```",[3107,3108,3109,3110,3113],{"name":3036,"color":3037},{"name":3022,"color":3023},{"name":3040,"color":3041},{"name":3111,"color":3112},"closed-by-bot","ededed",{"name":3114,"color":3112},"stale",3650,"The NavigationMenu's v-model does not update correctly","2025-06-18T09:01:24Z","https://github.com/nuxt/ui/issues/3650",0.6909557,{"description":3121,"labels":3122,"number":3128,"owner":3025,"repository":3026,"state":3065,"title":3129,"updated_at":3130,"url":3131,"score":3132},"### Description\n\nIs there any chance we can get option to enable/disable collapsible when collapsed prop is true. v3.0.0-alpha.13 'fixed' NavigationMenu: disable collapsible with collapsed prop, i used nuxt ui since v3.0.0-alpha.12 and thought the collapsible when collapsed was feature.\n\n### Additional context\n\n_No response_",[3123,3126,3127],{"name":3124,"color":3125},"enhancement","a2eeef",{"name":3022,"color":3023},{"name":3040,"color":3041},3353,"NavigationMenu: Option to enable collapsible with collapsed prop","2025-05-10T15:51:54Z","https://github.com/nuxt/ui/issues/3353",0.6948009,{"description":3134,"labels":3135,"number":3142,"owner":3025,"repository":3025,"state":3065,"title":3143,"updated_at":3144,"url":3145,"score":3146},"### Environment\n\n- Operating System: `Darwin`\r\n- Node Version: `v21.1.0`\r\n- Nuxt Version: `3.10.2`\r\n- CLI Version: `3.10.1`\r\n- Nitro Version: `2.8.1`\r\n- Package Manager: `npm@10.2.0`\r\n- Builder: `-`\r\n- User Config: `ssr`, `target`, `experimental`, `app`, `vue`, `css`, `modules`, `storyblok`, `build`, `vite`, `nitro`, `hooks`, `routeRules`, `imports`, `runtimeConfig`, `devtools`\r\n- Runtime Modules: `@storyblok/nuxt@6.0.4`, `@pinia/nuxt@0.5.1`\r\n- Build Modules: `-`\n\n### Reproduction\n\nhttps://stackblitz.com/edit/github-prqbf9?file=app.vue\n\n### Describe the bug\n\nIf you use a `nuxt-link` with the `custom` and `external` prop and click on it, a console.error will occur complaing about the nuxt-link not having the external prop set to true, even though it is.\r\n\r\nThe navigation itself still works, its just a console.error that occurs before you leave the page.\r\n\r\nThe interesting part is that the `replace` prop is respected, but not `external`.\n\n### Additional context\n\nI think the issue is coming from this file:\r\nhttps://github.com/nuxt/nuxt/blob/9326b7a8bde1ae793ba046f7dacc4ebbe200b786/packages/nuxt/src/app/components/nuxt-link.ts#L357C15-L357C23\r\n\r\nThe replace prop is included here, but not external.\n\n### Logs\n\n_No response_",[3136,3139],{"name":3137,"color":3138},"3.x","29bc7f",{"name":3140,"color":3141},"🔨 p3-minor","FBCA04",25866,"The `nuxt-link` component does not respect the external prop","2024-02-21T21:20:15Z","https://github.com/nuxt/nuxt/issues/25866",0.70003253,["Reactive",3148],{},["Set"],["ShallowReactive",3151],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fd9Q7TUoFj5t2eVDRArFm0WkFgpZa3GRVHqPC8o09-V8":-1},"/nuxt/ui/3911"]