\n\n### Additional context\n\n_No response_",[3020,3023,3026],{"name":3021,"color":3022},"enhancement","a2eeef",{"name":3024,"color":3025},"v3","49DCB8",{"name":3027,"color":3028},"triage","ffffff",4566,"nuxt","ui","open","Tooltip should not display when there is no value for 'text'","2025-07-22T06:39:46Z","https://github.com/nuxt/ui/issues/4566",0.7844986,{"description":3038,"labels":3039,"number":3044,"owner":3030,"repository":3031,"state":3045,"title":3046,"updated_at":3047,"url":3048,"score":3049},"### Environment\n\n- Operating System: Linux\n- Node Version: v23.4.0\n- Nuxt Version: 3.15.4\n- CLI Version: 3.21.1\n- Nitro Version: 2.10.4\n- Package Manager: bun@1.2.1\n- Builder: -\n- User Config: compatibilityDate, devtools, modules, runtimeConfig, auth, pinia, fonts, css, ui, app\n- Runtime Modules: @nuxt/ui@3.0.0-alpha.12, @sidebase/nuxt-auth@0.10.0, @nuxt/fonts@0.10.3, @pinia/nuxt@0.9.0\n- Build Modules: -\n\n\n\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\nhttps://github.com/StefanH-AT/NuxtUi3-Shortcut-Meta\n\n### Description\n\n[According to the docs](https://ui3.nuxt.dev/composables/define-shortcuts#usage), `meta` is supposed to be translated to `Ctrl`, but on Linux, the Linux Meta key, which is the same as the Windows key, is detected.\n\nI find the usage of the word \"meta\" confusing due to this double meaning. Meta is commonly used to refer to the Windows aka Super aka Meta key, but not as Control\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3040,3043],{"name":3041,"color":3042},"bug","d73a4a",{"name":3024,"color":3025},3220,"closed","Meta keyboard shortcut maps to system meta (\"Windows\") key on linux instead of Ctrl","2025-03-08T12:22:25Z","https://github.com/nuxt/ui/issues/3220",0.700886,{"description":3051,"labels":3052,"number":3058,"owner":3030,"repository":3031,"state":3045,"title":3059,"updated_at":3060,"url":3061,"score":3062},"### Description\n\nRight now, it's only possible to have checkboxes be in an indeterminate state as its initial state, and not be able to go back to that state after it has moved away from that state. My use case is a checkbox that is used to control a query parameter for filtering results.\n\n- Indeterminate state: `public = \u003Ctrue|false>` results are included. and when the checkbox is false, it filters that `public` field by the value of the checkbox. Effectively, `*`, `true`, and `false` states.\n\nDoesn't look as though this is possible today, with checkboxes, or with `Switch`.\n\nI have attempted to re-set the value to `indeterminate`, however, it looks as though the Checkbox ignores this state change.\n\n### Additional context\n\n_No response_",[3053,3054,3057],{"name":3021,"color":3022},{"name":3055,"color":3056},"needs reproduction","CB47CF",{"name":3024,"color":3025},3584,"feature(checkbox): support proper indeterminate state","2025-03-21T09:43:31Z","https://github.com/nuxt/ui/issues/3584",0.70138997,{"description":3064,"labels":3065,"number":3068,"owner":3030,"repository":3031,"state":3045,"title":3069,"updated_at":3047,"url":3070,"score":3071},"### Environment\n\n------------------------------\n- Operating System: Darwin\n- Node Version: v20.12.0\n- Nuxt Version: 3.15.4\n- CLI Version: 3.21.1\n- Nitro Version: 2.10.4\n- Package Manager: pnpm@10.4.1\n- Builder: -\n- User Config: extends, modules, $production, devtools, app, css, site, runtimeConfig, sourcemap, future, experimental, compatibilityDate, nitro, eslint, linkChecker, sitemap\n- Runtime Modules: @nuxt/ui-pro@3.0.0-alpha.13, @nuxtjs/seo@2.1.1, @nuxt/content@3.1.1, @sentry/nuxt/module@8.55.0\n- Build Modules: -\n------------------------------\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.0.0-alpha.13\n\n### Reproduction\n\nNo reproduction is needed. Prop.state is mutated.\n\n### Description\n\nThe current implementation of the Form component has two significant issues:\n\n\n1. **Direct Prop Mutation**: The component directly mutates its `state` prop, which violates Vue's fundamental rules about prop mutation. From Vue's documentation: [https://vuejs.org/guide/components/props.html#one-way-data-flow](https://vuejs.org/guide/components/props.html#one-way-data-flow)\n> \"All props form a one-way-down binding between the child property and the parent one: when the parent property updates, it will flow down to the child, but not the other way around. This prevents child components from accidentally mutating the parent's state, which can make your app's data flow harder to understand.\"\n\n2. **Breaks Immutable State Patterns**: The direct mutation approach is incompatible with modern state management patterns that rely on immutable state updates.\n\nThe problematic code is in the `_validate` function:\n```typescript\nif (opts.transform) {\n Object.assign(props.state, transformedState.value)\n}\n\n```\n\nhttps://github.com/nuxt/ui/blob/v3/src/runtime/components/Form.vue\n\nLine 182",[3066,3067],{"name":3041,"color":3042},{"name":3024,"color":3025},3354,"Form component violates Vue prop mutation rules and breaks immutable state patterns","https://github.com/nuxt/ui/issues/3354",0.7225491,{"description":3073,"labels":3074,"number":3078,"owner":3030,"repository":3079,"state":3045,"title":3080,"updated_at":3081,"url":3082,"score":3083},"### Environment\n\n- Operating System: `Darwin`\r\n- Node Version: `v21.5.0`\r\n- Nuxt Version: `3.9.0`\r\n- CLI Version: `3.10.0`\r\n- Nitro Version: `2.8.1`\r\n- Package Manager: `npm@10.2.4`\r\n- Builder: `-`\r\n- User Config: `alias`, `app`, `devtools`, `eslint`, `i18n`, `imports`, `modules`, `nitro`, `runtimeConfig`, `ssr`, `testUtils`, `typescript`, `vite`, `vuetify`\r\n- Runtime Modules: `@pinia-plugin-persistedstate/nuxt@1.2.0`, `@pinia/nuxt@0.5.1`, `@nuxtjs/i18n@8.0.0`, `@nuxtjs/eslint-module@4.1.0`, `nuxt-typed-router@3.5.0`, `@nuxt/test-utils/module@3.9.0`, `vuetify-nuxt-module@0.7.3`, `nuxt-lodash@2.5.3`\r\n- Build Modules: `-`\r\n\n\n### Reproduction\n\nhttps://stackblitz.com/edit/github-cyqbu8\n\n### Describe the bug\n\nAfter upgrading to 3.9.0, I am getting errors when running tests due to missing identifiers in the nuxt package. Reproduction shows error from my middleware test but I get similar errors when running component tests but this time the error is \"Error: Missing \"#build/paths.mjs\" specifier in \"nuxt\" package\"\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[3075],{"name":3076,"color":3077},"pending triage","5D08F5",679,"test-utils","Error running test after upgrade to 3.9.0","2024-01-28T11:25:59Z","https://github.com/nuxt/test-utils/issues/679",0.7427943,{"description":3085,"labels":3086,"number":3092,"owner":3030,"repository":3031,"state":3045,"title":3093,"updated_at":3094,"url":3095,"score":3096},"### Environment\n\n- Operating System: Darwin\n- Node Version: v22.11.0\n- Nuxt Version: 3.16.0\n- CLI Version: 3.22.5\n- Nitro Version: 2.11.6\n- Package Manager: pnpm@9.15.4\n- Builder: -\n- User Config: modules, devtools, app, css, runtimeConfig, future, compatibilityDate, telemetry, eslint\n- Runtime Modules: @nuxt/ui-pro@3.0.0, @nuxt/eslint@1.0.1, @vueuse/nuxt@12.5.0, @nuxt/image@1.9.0\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3\n\n### Reproduction\n\nsee below\n\n### Description\n\nI get the follwing error:\n\n```\nruntime-core.esm-bundler.js:51 [Vue warn]: injection \"Symbol(nuxt-ui.locale-context)\" not found. \n at \u003CUSlideover open=false onUpdate:open=fn side=\"left\" ... > \n at \u003CUDashboardSidebar collapsible=\"\" resizable=\"\" > \n at \u003CPrimitive as=undefined class=\"fixed inset-0 flex overflow-hidden\" > \n at \u003CUDashboardGroup> \n at \u003CDefault ref=Ref\u003C undefined > > \n at \u003CAsyncComponentWrapper ref=Ref\u003C undefined > > \n at \u003CLayoutLoader key=\"default\" layoutProps= Object name=\"default\" > \n at \u003CNuxtLayoutProvider layoutProps= Object key=\"default\" name=\"default\" ... > \n at \u003CNuxtLayout> \n at \u003CApp key=4 > \n at \u003CNuxtRoot>\n```\n\nwhen usinng the DashboardSidebar component:\n```\n \u003CUDashboardSidebar\n collapsible\n resizable\n >\n \u003Ctemplate #header>\n \u003Cdiv class=\"flex items-center gap-2\">\n \u003CUIcon\n name=\"i-solar-buildings-2-bold\"\n class=\"w-7 h-7\"\n />\n \u003Cspan class=\"flex items-center gap-2 font-semibold text-lg logo\">example\u003C/span>\n \u003C/div>\n \u003C/template>\n \u003CUNavigationMenu\n orientation=\"vertical\"\n :items=\"links\"\n />\n \u003Cdiv class=\"flex-1\" />\n \u003CUNavigationMenu\n orientation=\"vertical\"\n :items=\"footerLinks\"\n />\n \u003CUSeparator class=\"sticky bottom-0\" />\n \u003Ctemplate #footer>\n \u003Cspan class=\"text-xs text-neutral-500 tracking-tight\">Version {{ useRuntimeConfig().public.version }}\u003C/span>\n \u003C/template>\n \u003C/UDashboardSidebar>\n\n```\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3087,3088,3089],{"name":3041,"color":3042},{"name":3024,"color":3025},{"name":3090,"color":3091},"pro","5BD3CB",3549,"injection \"Symbol(nuxt-ui.locale-context)\" not found","2025-03-18T11:12:44Z","https://github.com/nuxt/ui/issues/3549",0.7440444,{"description":3098,"labels":3099,"number":3102,"owner":3030,"repository":3031,"state":3045,"title":3103,"updated_at":3104,"url":3105,"score":3106},"### Environment\n\n- Operating System: Windows_NT\n- Node Version: v22.11.0\n- Nuxt Version: 3.15.1\n- CLI Version: 3.20.0\n- Nitro Version: 2.10.4\n- Package Manager: bun@1.1.37\n- Builder: -\n- User Config: components, css, extends, modules, ui, supabase, i18n, app, mapbox, runtimeConfig, compatibilityDate\n- Runtime Modules: nuxt-mapbox@1.6.1, @nuxt/image@1.9.0, @nuxt/ui@3.0.0-alpha.10, @nuxtjs/supabase@1.4.5, @vueuse/nuxt@10.11.1, @nuxtjs/i18n@8.5.6, @vueuse/motion/nuxt@2.2.6 \n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.0.0-alpha.10\n\n### Reproduction\n\nhttps://codesandbox.io/p/devbox/quizzical-wood-ntyxty\n\n### Description\n\nwhen a child item at the second level has more than three levels of nested children, the collapse button for that second-level item stops working.\n\nI'm using the following code snippet:\nIs this a known limitation of the UNavigationMenu component, or could it be a bug?\n\nI would greatly appreciate any guidance on how to resolve this issue and ensure the collapse \nTypeScript\n```\n\u003Cscript setup lang=\"ts\">\n const items = ref([\n {\n label: 'Home',\n icon: 'i-tabler-home',\n description: 'Fully styled and customizable components for Nuxt.',\n children: [\n {\n label: 'Introduction 2',\n description: 'Fully styled and customizable components for Nuxt.',\n icon: 'i-lucide-house',\n children: [\n {\n label: 'Getting Started 3',\n description: 'Learn how to get started with Reka UI.',\n icon: 'i-tabler-star',\n to: '/',\n },\n {\n label: 'Installation 3',\n description: 'Learn how to get started with Reka UI in your Nuxt project.',\n icon: 'i-lucide-house',\n to: '/',\n },\n ],\n },\n ],\n },\n ])\n\u003C/script>\n\n\u003Ctemplate>\n \u003CUNavigationMenu\n orientation=\"vertical\"\n :items=\"links\"\n color=\"neutral\"\n :ui=\"{\n link: 'group relative flex items-center gap-2 px-3 py-2 font-bold rounded-md text-md focus:outline-none focus-visible:outline-none dark:focus-visible:outline-none focus-visible:before:ring-inset focus-visible:before:ring-2 focus-visible:before:ring-primary-500 dark:focus-visible:before:ring-primary-400 before:absolute before:inset-px before:rounded-md disabled:cursor-not-allowed disabled:opacity-75',\n }\"\n />\n\u003C/template>\n\n```\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3100,3101],{"name":3041,"color":3042},{"name":3024,"color":3025},3069,"UNavigationMenu I'm facing an issue with the collapse functionality of my nested navigation menu.","2025-01-25T12:56:13Z","https://github.com/nuxt/ui/issues/3069",0.74881816,{"description":3108,"labels":3109,"number":3111,"owner":3030,"repository":3031,"state":3045,"title":3112,"updated_at":3113,"url":3114,"score":3115},"Currently, portal components (modals, popovers, etc.) are directly attached to the root of the body. It would be beneficial to allow specifying their destination within the configuration .This would provide greater control over rendering order and potential styling conflicts, especially in complex applications with open shadow Dom. \n\nFor instance, a developer might want to render a modal within a specific container to inherit styles or avoid interference with other elements on the page (I currently using Nuxt ui as a web component withing WordPress). \n\nThe proposed configuration option could be a CSS selector string, allowing for flexible targeting of any existing element in the DOM defaulting to 'body'. ",[3110],{"name":3024,"color":3025},3687,"Allow specify portal destination for all portaled components","2025-04-21T15:42:56Z","https://github.com/nuxt/ui/issues/3687",0.7498418,{"description":3117,"labels":3118,"number":3121,"owner":3030,"repository":3122,"state":3045,"title":3123,"updated_at":3124,"url":3125,"score":3126},"\n",[3119],{"name":3021,"color":3120},"1ad6ff",127,"nuxt.com","Hide Transfer section if no available destinations","2023-02-15T12:30:41Z","https://github.com/nuxt/nuxt.com/issues/127",0.7519774,{"description":3128,"labels":3129,"number":3133,"owner":3030,"repository":3031,"state":3045,"title":3134,"updated_at":3135,"url":3136,"score":3137},"### Description\n\nWhile most components support the theming props (globally via app.config and as local props) the UForm component doesn't. For consistency it'd be great if this could be added to the Form component too.\n\n### Additional context\n\n_No response_",[3130,3131,3132],{"name":3021,"color":3022},{"name":3024,"color":3025},{"name":3027,"color":3028},3752,"Form Component: Support theming props","2025-04-10T19:55:39Z","https://github.com/nuxt/ui/issues/3752",0.75332767,["Reactive",3139],{},["Set"],["ShallowReactive",3142],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fDIjjNUNKLYuAxZYgXTByMvrignH5Py_uynNb_U7W9N8":-1},"/nuxt/ui/3218"]