` component, specifically with the `v-model:open` binding:\n\n* `v-model:collapsed` works great — it properly handles the collapsed/expanded state.\n* But `v-model:open` doesn't seem to behave as expected. When I bind it to a custom `open` state and try to set it to `false` (e.g., using a custom button), the sidebar doesn’t actually close. Then, as soon as I click anywhere else on the page, the `open` value is automatically reset to `true`.\n\nIt feels like something internal is re-opening the sidebar and overriding the bound value.\n\nOther small notes:\n\n* `\u003CUDashboardSidebarToggle />` is hidden on desktop due to `lg:hidden`, which makes sense for mobile setups. But even when made visible, it doesn’t allow fully toggling the sidebar on desktop — the sidebar remains fixed.\n* I also tried changing the `default-size` prop (e.g., to `16rem` / `256px`), and it didn’t apply immediately. It only worked after clearing the site data. I’m guessing this is due to cookies storing the previous value? Maybe it could be possible to sync the cookie automatically when `default-size` changes?\n\nHere’s a minimal reproduction of the issue: [Here](https://codesandbox.io/p/devbox/polished-cookies-lrv5hm?file=%2Fapp%2Fpages%2Findex.vue%3A9%2C23)\n\nLastly, I was wondering if in the future it might be possible to support a prop like `expand-on-hover`, where a collapsed sidebar could temporarily expand on mouse hover — without pushing the rest of the layout. This could allow building more advanced layouts similar to what Supabase uses: a primary sidebar that stays collapsed when a secondary one is open, but can still expand on hover without shifting the content.\n\nThanks again for your amazing work and for considering these ideas! 😊\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3157,3158,3159],{"name":3138,"color":3139},{"name":3141,"color":3142},{"name":3144,"color":3145},4599,"DashboardSidebar: v-model:open not working as expected","2025-07-25T16:31:55Z","https://github.com/nuxt/ui/issues/4599",0.68718845,{"description":3166,"labels":3167,"number":3171,"owner":3147,"repository":3148,"state":3149,"title":3172,"updated_at":3173,"url":3174,"score":3175},"### Environment\n\n- Operating System: Darwin\n- Node Version: v23.11.0\n- Nuxt Version: 3.17.3\n- CLI Version: 3.25.1\n- Nitro Version: 2.11.12\n- Package Manager: npm@10.9.2\n- Builder: -\n- User Config: devtools, typescript, css, compatibilityDate, devServer, vite, runtimeConfig, app, ui, scripts, modules, sentry, sourcemap\n- Runtime Modules: @nuxt/ui@3.1.2, @pinia/nuxt@0.11.0, pinia-plugin-persistedstate/nuxt@4.3.0, @sentry/nuxt/module@9.19.0, @nuxt/scripts@0.11.7, @nuxt/eslint@1.4.0\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\nhttps://codesandbox.io/p/devbox/r7ryl3\n\n### Description\n\nI recently upgrade to NuxtUI 3.1.2 (from 3.0.1) and It's impossible (or I don't know) how to deal with custom type for `InputMenu`, I got some types issues on `label-key`, `v-model`, `items`, `slots` as you can see in my reproduction.\n\n### Additional context\n\n\n\n### Logs\n\n```shell-script\n\n```",[3168,3169,3170],{"name":3138,"color":3139},{"name":3141,"color":3142},{"name":3144,"color":3145},4182,"Custom type with InputMenu","2025-05-19T12:22:28Z","https://github.com/nuxt/ui/issues/4182",0.6897029,{"description":3177,"labels":3178,"number":3182,"owner":3147,"repository":3148,"state":3183,"title":3184,"updated_at":3185,"url":3186,"score":3187},"### Environment\n\n```\n- Operating System: Darwin\n- Node Version: v22.14.0\n- Nuxt Version: 3.16.2\n- CLI Version: 3.24.1\n- Nitro Version: 2.11.9\n- Package Manager: bun@1.2.9\n- Builder: -\n- User Config: ssr, imports, devtools, experimental, future, compatibilityDate, alias, runtimeConfig, devServer, app, css, modules, build, hooks, dayjs, ui, typescript\n- Runtime Modules: @nuxt/eslint@1.3.0, @vueuse/nuxt@13.1.0, @nuxt/test-utils/module@3.17.2, dayjs-nuxt@2.1.11, nuxt-svgo@4.0.17, @nuxt/ui-pro@3.1.0, @pinia/nuxt@0.11.0, @pinia/colada-nuxt@0.1.1, @nuxt/image@1.10.0\n- Build Modules: -\n```\n\n\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\n3.1.0\n\n### Reproduction\n\nhttps://codesandbox.io/p/devbox/empty-fast-5xtcmy?workspaceId=ws_SD2P6X4ufyWkm2P3aqoQA6\n\n### Description\n\nbetween version 3.0.2 and 3.1.0 the content container for the menu items is no longer filling the width.\n\n### Additional context\n\n__no response__\n\n### Logs\n\n```shell-script\n\n```",[3179,3180,3181],{"name":3138,"color":3139},{"name":3141,"color":3142},{"name":3144,"color":3145},3987,"closed","[NavigationMenu] Regression - Update","2025-05-02T09:52:45Z","https://github.com/nuxt/ui/issues/3987",0.6572639,{"description":3189,"labels":3190,"number":3194,"owner":3147,"repository":3148,"state":3183,"title":3195,"updated_at":3196,"url":3197,"score":3198},"### Environment\n\n- Operating System: Windows_NT\n- Node Version: v24.0.2\n- Nuxt Version: 3.17.4\n- CLI Version: 3.25.1\n- Nitro Version: 2.11.12\n- Package Manager: bun@1.2.14\n- Builder: -\n- User Config: compatibilityDate, devtools, future, modules, css, runtimeConfig\n- Runtime Modules: @nuxt/ui-pro@3.1.3, @nuxtjs/supabase@1.5.1, @nuxt/image@1.10.0\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\nNo need for reproduction.\n\n### Description\n\nHi, and thanks for this amazing UI library.\nI was wondering why to use a v-model for UProgress since it does not update the script from the dom?\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3191,3192,3193],{"name":3138,"color":3139},{"name":3141,"color":3142},{"name":3144,"color":3145},4232,"[UProgress]: replace v-model with :value?","2025-05-27T12:32:29Z","https://github.com/nuxt/ui/issues/4232",0.67665535,{"description":3200,"labels":3201,"number":3205,"owner":3147,"repository":3147,"state":3183,"title":3206,"updated_at":3207,"url":3208,"score":3209},"### Environment\n\n- Operating System: `Darwin`\n- Node Version: `v20.10.0`\n- Nuxt Version: `3.14.1592`\n- CLI Version: `3.15.0`\n- Nitro Version: `2.10.4`\n- Package Manager: `pnpm@9.7.0`\n- Builder: `-`\n- User Config: `-`\n- Runtime Modules: `-`\n- Build Modules: `-`\n\n### Reproduction\n\nhttps://stackblitz.com/edit/github-ynphxo8p?file=app.vue\n\n### Describe the bug\n\nThe `defineModel` function works as expected in Vue's playground but does not work in a Nuxt project. I copied the exact same code from Vue's playground into my Nuxt project, but it fails to function correctly.\n\n### Expected Behavior\nThe `defineModel` function should work as it does in [Vue's playground](https://play.vuejs.org/#eNqFUtFKwzAU/ZWYl06YLbK30Q10DFSYigq+5KW0t11mmoQknZPSf/cm3eqEsT0l555zuefmpKV3WsfbBuiUpjY3XDtiwTV6ziSvtTKOLNZcFKQ0qiZRnATkG6JB0BIDJen2kp5iMlfSOlLbisw8P4oeQAhFPpURxVV0zWSa9PNwEgIHtRaZA0SEpOvbeduG5q5LE0Sh2jvZ3tSqADFjFHlGSYJkmhz10zF1FseXvIo3VklcrfX9jOaq1lyAedGOoz1GpyQwnsvQ3fdTqDnTwPhQz9eQf52ob+zO1xh9NWDBbIHRgXOZqcD19PL9GXZ4H0h03whUnyHfwCrReI+97L6RBdo+0gW3j+H9uaw+7HLnQNrDUt6oV3ZBzyhmsjiz+p/dSTwJfUx2+IpD1ic+xz5enwQGXEDJJaw8Gl2I1upMzlc/hEvdOBR6SNKAjqP1J6P/o6XdL11L5h4=), allowing two-way binding between the component's model and the parent.\n\n### Actual Behavior\nThe `defineModel` function does not behave as expected, the value of the input is not updating.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3202],{"name":3203,"color":3204},"pending triage","E99695",30205,"defineModel Not Working in Nuxt 3 Despite Working in Vue's Playground","2024-12-09T13:38:08Z","https://github.com/nuxt/nuxt/issues/30205",0.6773092,{"description":3211,"labels":3212,"number":3218,"owner":3147,"repository":3148,"state":3183,"title":3219,"updated_at":3220,"url":3221,"score":3222},"### 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```",[3213,3214,3217],{"name":3138,"color":3139},{"name":3215,"color":3216},"duplicate","cfd3d7",{"name":3141,"color":3142},4005,"Tab slots types error","2025-04-28T10:54:47Z","https://github.com/nuxt/ui/issues/4005",0.6839154,{"description":3224,"labels":3225,"number":3229,"owner":3147,"repository":3148,"state":3183,"title":3230,"updated_at":3231,"url":3232,"score":3233},"### Environment\n\nnot needed\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.1.1\n\n### Reproduction\n\ncheck current docs: https://ui.nuxt.com/components/navigation-menu#content-orientation\n\n### Description\n\n\n\nThe dropdown is at wrong position... also the \"arrow\" prop doesnt work\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3226,3227,3228],{"name":3138,"color":3139},{"name":3141,"color":3142},{"name":3144,"color":3145},4073,"UNavigationMenu: Dropdown broken","2025-05-13T12:02:03Z","https://github.com/nuxt/ui/issues/4073",0.6862172,{"description":3235,"labels":3236,"number":3239,"owner":3147,"repository":3148,"state":3183,"title":3240,"updated_at":3241,"url":3242,"score":3243},"### Environment\n\n- Operating System: Linux\n- Node Version: v22.14.0\n- Nuxt Version: 3.17.3\n- CLI Version: 3.25.1\n- Nitro Version: 2.11.12\n- Package Manager: npm@11.3.0\n- Builder: -\n- User Config: app, build, colorMode, compatibilityDate, debug, devtools, fonts, future, hooks, i18n, icon, imports, modules, nitro, routeRules, runtimeConfig, security, ssr, sourcemap, css, telemetry, vite\n- Runtime Modules: @nuxt/eslint@1.3.1, @pinia/nuxt@0.11.0, @vueuse/nuxt@13.2.0, @nuxtjs/i18n@9.5.4, nuxt-security@2.2.0, @nuxt/ui@3.1.2\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\nhttps://codesandbox.io/p/devbox/sharp-christian-kzdxt9?file=%2Fapp%2Fpages%2Findex.vue\n\n### Description\n\nStarting from v3.1.2, using the [built-in v-model-modifiers](https://vuejs.org/guide/essentials/forms.html#modifiers) produces type errors. They are still working tho, so its only a type issue.\n\nReproduction:\n1. Open provided link\n2. Run `pnpx nuxi typecheck`\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n➜ workspace git:(master) ✗ pnpx nuxi typecheck\nPackages: +1\n+\nProgress: resolved 1, reused 1, downloaded 0, added 1, done\nℹ Nuxt Icon server bundle mode is set to local 11:09:23 AM\n✔ Nuxt Icon discovered local-installed 2 collections: lucide, simple-icons 11:09:25 AM\nℹ Running with compatibility version 4 nuxt 11:09:25 AM\napp/pages/index.vue:8:22 - error TS2353: Object literal may only specify known properties, and 'modelModifiers' does not exist in type '{ readonly onBlur?: ((event: FocusEvent) => any) | undefined; readonly onChange?: ((event: Event) => any) | undefined; readonly \"onUpdate:modelValue\"?: ((payload: number) => any) | undefined; ... 24 more ...; modelValue?: number | undefined; } & VNodeProps & AllowedComponentProps & ComponentCustomProps'.\n\n8 \u003CUInput v-model.number=\"myNumber\" type=\"number\" />\n ~~~~~~~\n\napp/pages/index.vue:9:22 - error TS2353: Object literal may only specify known properties, and 'modelModifiers' does not exist in type '{ readonly onBlur?: ((event: FocusEvent) => any) | undefined; readonly onChange?: ((event: Event) => any) | undefined; readonly \"onUpdate:modelValue\"?: ((payload: string) => any) | undefined; ... 24 more ...; modelValue?: string | undefined; } & VNodeProps & AllowedComponentProps & ComponentCustomProps'.\n\n9 \u003CUInput v-model.lazy=\"myText\" />\n ~~~~~\n\n\nFound 2 errors in the same file, starting at: app/pages/index.vue:8\n\n\n ERROR Process exited with non-zero status (2) 11:09:41 AM\n\n at R._waitForOutput (/root/.cache/pnpm/v3/tmp/dlx-4483/node_modules/.pnpm/nuxi@3.25.1/node_modules/nuxi/dist/chunks/main.mjs:508:13)\n at process.processTicksAndRejections (node:internal/process/task_queues:95:5)\n at async Object.run (/root/.cache/pnpm/v3/tmp/dlx-4483/node_modules/.pnpm/nuxi@3.25.1/node_modules/nuxi/dist/chunks/typecheck.mjs:91:9)\n at async runCommand$1 (/root/.cache/pnpm/v3/tmp/dlx-4483/node_modules/.pnpm/nuxi@3.25.1/node_modules/nuxi/dist/shared/nuxi.BlFGnQYG.mjs:1767:16)\n at async runCommand$1 (/root/.cache/pnpm/v3/tmp/dlx-4483/node_modules/.pnpm/nuxi@3.25.1/node_modules/nuxi/dist/shared/nuxi.BlFGnQYG.mjs:1758:11)\n at async runMain$1 (/root/.cache/pnpm/v3/tmp/dlx-4483/node_modules/.pnpm/nuxi@3.25.1/node_modules/nuxi/dist/shared/nuxi.BlFGnQYG.mjs:1896:7) \n\n\n\n ERROR Process exited with non-zero status (2)\n```",[3237,3238],{"name":3138,"color":3139},{"name":3141,"color":3142},4166,"Built-in v-model modifiers produce type errors with v3.1.2","2025-05-22T12:51:25Z","https://github.com/nuxt/ui/issues/4166",0.690915,{"description":3245,"labels":3246,"number":3254,"owner":3147,"repository":3148,"state":3183,"title":3255,"updated_at":3256,"url":3257,"score":3258},"### Environment\n\n------------------------------\n- Operating System: Darwin\n- Node Version: v22.13.1\n- Nuxt Version: 3.16.2\n- CLI Version: 3.24.1\n- Nitro Version: 2.11.8\n- Package Manager: pnpm@10.8.1\n- Builder: -\n- User Config: app, compatibilityDate, css, devtools, devServer, eslint, imports, modules, nitro, runtimeConfig, sourcemap, ssr, fonts, icon, ui, colorMode\n- Runtime Modules: @nuxt/eslint@1.3.0, @nuxt/ui@3.0.2, @vueuse/nuxt@13.0.0\n- Build Modules: -\n------------------------------\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\n3.16.2\n\n### Reproduction\n\nhttps://codesandbox.io/p/devbox/amazing-cdn-vgydgy\n\n### Description\n\nI want to close `UContextMenu` programmatically by setting `v-model:open` to `false`, but it doesn’t close the menu as expected.\n\n## Reproduction:\n```\n\u003Ctemplate>\n \u003Cdiv class=\"flex flex-col items-center justify-center gap-4 h-screen\">\n \u003CUContextMenu v-model:open=\"contextMenuOpen\" :items=\"menuItems\">\n \u003Cdiv class=\"w-50 h-20 border-1 rounded flex items-center justify-center bg-slate-500\">Right Click Here\u003C/div>\n \u003C/UContextMenu>\n \u003Cdiv class=\"mt-5\">contextMenuOpen: {{contextMenuOpen}}\u003C/div>\n \u003C/div>\n\u003C/template>\n\n\u003Cscript lang=\"ts\" setup>\nconst contextMenuOpen = ref(false)\n\nconst menuItems = [[\n {\n label: 'Item1'\n },\n {\n label: 'Item2'\n }\n]]\n\nwatch(contextMenuOpen,(newValue)=>{\n if(newValue){\n setTimeout(()=>{\n contextMenuOpen.value = false\n }, 3000)\n }\n})\n\u003C/script>\n```\n\n## What happens\nAfter opening the context menu and waiting for 3 seconds, `contextMenuOpen` is set to `false`, but the menu remains open.\n\n## What I expected\nWhen `contextMenuOpen` becomes `false`, the context menu should close.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3247,3250,3251],{"name":3248,"color":3249},"enhancement","a2eeef",{"name":3141,"color":3142},{"name":3252,"color":3253},"reka-ui","56d799",4107,"Cannot close `UContextMenu` programmatically via `v-model:open` = false","2025-05-10T15:45:52Z","https://github.com/nuxt/ui/issues/4107",0.69176203,["Reactive",3260],{},["Set"],["ShallowReactive",3263],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$f_TU9ys81GqpMo9vXo-AouYzSUtCrbdI12aRxLULORKI":-1},"/nuxt/ui/3650"]