\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```",[3177,3180,3181],{"name":3178,"color":3179},"bug","d73a4a",{"name":3152,"color":3153},{"name":3182,"color":3183},"pro","5BD3CB",3549,"injection \"Symbol(nuxt-ui.locale-context)\" not found","2025-03-18T11:12:44Z","https://github.com/nuxt/ui/issues/3549",0.76248884,{"description":3190,"labels":3191,"number":3193,"owner":3155,"repository":3156,"state":3157,"title":3194,"updated_at":3195,"url":3196,"score":3197},"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'. ",[3192],{"name":3152,"color":3153},3687,"Allow specify portal destination for all portaled components","2025-04-21T15:42:56Z","https://github.com/nuxt/ui/issues/3687",0.7718717,{"description":3199,"labels":3200,"number":3203,"owner":3155,"repository":3204,"state":3157,"title":3205,"updated_at":3206,"url":3207,"score":3208},"https://nuxt.com/support/us",[3201],{"name":3178,"color":3202},"ff281a",1167,"nuxt.com","Sponsors page does not show any sponsors","2023-06-06T12:14:43Z","https://github.com/nuxt/nuxt.com/issues/1167",0.7762368,{"description":3210,"labels":3211,"number":3219,"owner":3155,"repository":3156,"state":3157,"title":3220,"updated_at":3221,"url":3222,"score":3223},"### 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_",[3212,3215,3216],{"name":3213,"color":3214},"enhancement","a2eeef",{"name":3152,"color":3153},{"name":3217,"color":3218},"triage","ffffff",3752,"Form Component: Support theming props","2025-04-10T19:55:39Z","https://github.com/nuxt/ui/issues/3752",0.7850588,{"description":3225,"labels":3226,"number":3229,"owner":3155,"repository":3156,"state":3157,"title":3230,"updated_at":3231,"url":3232,"score":3233},"### 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```",[3227,3228],{"name":3178,"color":3179},{"name":3152,"color":3153},3220,"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.7857428,{"description":3235,"labels":3236,"number":3239,"owner":3155,"repository":3156,"state":3157,"title":3240,"updated_at":3231,"url":3241,"score":3242},"### 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",[3237,3238],{"name":3178,"color":3179},{"name":3152,"color":3153},3354,"Form component violates Vue prop mutation rules and breaks immutable state patterns","https://github.com/nuxt/ui/issues/3354",0.7864929,{"description":3244,"labels":3245,"number":3247,"owner":3155,"repository":3204,"state":3157,"title":3248,"updated_at":3249,"url":3250,"score":3251},"",[3246],{"name":3178,"color":3202},411,"When first going to a project, the `default_branch` is not selected but instead the first element in array","2023-02-15T12:32:16Z","https://github.com/nuxt/nuxt.com/issues/411",0.7926995,{"description":3253,"labels":3254,"number":3259,"owner":3155,"repository":3156,"state":3157,"title":3260,"updated_at":3261,"url":3262,"score":3263},"### Description\n\nHello, i was wondering if its possible to create something similar to this perhaps using the existing radio-group component.\r\n\r\nExample: https://tailwindui.com/components/application-ui/forms/radio-groups\r\n\u003Cimg width=\"1201\" alt=\"Screenshot 2024-01-11 at 7 59 09 PM\" src=\"https://github.com/nuxt/ui/assets/33962719/5c1bd9cb-7c96-4306-83c5-46eda713de10\">\r\n\n\n### Additional context\n\n_No response_",[3255,3256,3257],{"name":3146,"color":3147},{"name":3213,"color":3214},{"name":3258,"color":3218},"wontfix-v2",1221,"Radio Groups cards","2025-03-24T15:01:33Z","https://github.com/nuxt/ui/issues/1221",0.79479367,["Reactive",3265],{},["Set"],["ShallowReactive",3268],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fIf3cJ0uNhGaQdvD7xnQz83a-Ms7DBzgFWvHunlDJCb4":-1},"/nuxt/ui/3584"]