\n```\n\n\n### Description\n\nWhen using `UInputMenu`, each item can be assigned a custom class. However, after filtering, the class assignment seems to mismatch. For example, the \"Green\" item may be displayed in red color.\n\n### Additional context\n\n- Initial state (before filtering): \n\u003Cimg width=\"328\" height=\"243\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/f556d5b4-554e-4328-98f1-e3bb037504bf\" />\n\n- After filtering with \"r\": \n\u003Cimg width=\"338\" height=\"206\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/bbed6c9b-2eae-4c55-9d68-2991f64c26ca\" />\n\nIn the filtered state, the \"Green\" item is incorrectly displayed in red.\n\n### Logs\n\n```shell-script\n\n```",[3176,3177,3178],{"name":3146,"color":3147},{"name":3149,"color":3150},{"name":3152,"color":3153},4752,"UInputMenu item class mismatch after filtering","2025-08-15T01:57:20Z","https://github.com/nuxt/ui/issues/4752",0.6781874,{"description":3185,"labels":3186,"number":3190,"owner":3155,"repository":3156,"state":3157,"title":3191,"updated_at":3192,"url":3193,"score":3194},"### Environment\n\n- Operating System: Darwin\n- Node Version: v24.7.0\n- Nuxt Version: 3.19.1\n- CLI Version: 3.28.0\n- Nitro Version: 2.12.5\n- Package Manager: npm@11.5.1\n- Builder: -\n- User Config: devtools, typescript, css, compatibilityDate, devServer, vite, runtimeConfig, app, ui, scripts, piniaPluginPersistedstate, modules, sentry, sourcemap\n- Runtime Modules: @nuxt/ui@3.3.3, @pinia/nuxt@0.11.2, pinia-plugin-persistedstate/nuxt@4.5.0, @sentry/nuxt/module@10.10.0, @nuxt/scripts@0.11.13, @nuxt/eslint@1.9.0, nuxt-charts@0.2.3\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.3.3\n\n### Reproduction\n\nhttps://codesandbox.io/p/devbox/nuxt-ui-select-reproducible-forked-2238hh?workspaceId=ws_66GCezx3N94KbEtkfR1vKb\n\nIn my reproducible I use Nuxt V4 but it's the same behavior with Nuxt V3\n\n### Description\n\nActually the create emit is triggered after the change one, so it make some strange reactivity issues (because we rely on the change event for our server updates in some cases), actually we simply put a `setTimeout` on the change emit as a workarround but I didn't think it's a good solution 🥲\n\nI think there is the same issue on the SelectMenu too (I haven't tested it)\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3187,3188,3189],{"name":3146,"color":3147},{"name":3149,"color":3150},{"name":3152,"color":3153},4664,"InputMenu emit order","2025-09-08T15:55:07Z","https://github.com/nuxt/ui/issues/4664",0.6853703,{"description":3196,"labels":3197,"number":3201,"owner":3155,"repository":3156,"state":3157,"title":3202,"updated_at":3203,"url":3204,"score":3205},"### Environment\n\n- Operating System: Linux\n- Node Version: v24.4.1\n- Nuxt Version: 3.18.0\n- CLI Version: 3.27.0\n- Nitro Version: 2.12.4\n- Package Manager: npm@11.4.2\n- Builder: -\n- User Config: devtools, ssr, security, sourcemap, vite, sentry, future, compatibilityDate, css, modules, runtimeConfig, app\n- Runtime Modules: @nuxt/ui-pro@3.3.2, @nuxt/eslint@1.7.1, nuxt-security@2.3.0, @vueuse/nuxt@13.6.0, @sentry/nuxt/module@9.43.0\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Package\n\nv3.x\n\n### Version\n\nv3.18.0\n\n### Reproduction\n\nhttps://codesandbox.io/p/devbox/rspshv\n\n### Description\n\nWhen working with slideovers, if we open it from a DropdownMenu, an outside click is triggered, directly closing the slideover after opening.\n\nIf we add a timeout before opening, the outside click is triggered befor the slideover is opened, hence producing the expected behavior\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3198,3199,3200],{"name":3146,"color":3147},{"name":3149,"color":3150},{"name":3152,"color":3153},4839,"Slideover does not work when called from DropdownMenu","2025-09-01T06:45:41Z","https://github.com/nuxt/ui/issues/4839",0.6871387,{"description":3207,"labels":3208,"number":3211,"owner":3155,"repository":3156,"state":3212,"title":3213,"updated_at":3214,"url":3215,"score":3216},"### Environment\n\n------------------------------\n- Operating System: Darwin\n- Node Version: v20.19.2\n- Nuxt Version: -\n- CLI Version: 3.28.0\n- Nitro Version: -\n- Package Manager: npm@10.8.2\n- Builder: -\n- User Config: -\n- Runtime Modules: -\n- Build Modules: -\n------------------------------\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Package\n\nv3.x\n\n### Version\n\nv3.3.3\n\n### Reproduction\n\nhttps://stackblitz.com/edit/github-mj4wqh54?file=app%2Fpages%2Findex.vue\n\n### Description\n\nWhen using `InputMenu`, `Select` or `SelectMenu`, if the `modelValue` is `null` (or another falsy value) and an option with this value exists, its `label` is not displayed.\n\n**Expected behavior**:\nIf an option with a `null` (or falsy) value is present in the `options`, its `label` should be displayed when selected.\n\n**Example**:\n\n```vue\n\u003CUSelect\n v-model=\"value\"\n :items=\"[\n { name: '- Tout -', slug: null },\n { name: 'Sport', slug: 'sport' },\n { name: 'Culture', slug: 'culture' },\n ]\"\n value-key=\"slug\"\n label-key=\"name\"\n />\n```\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3209,3210],{"name":3146,"color":3147},{"name":3149,"color":3150},4869,"closed","InputMenu/Select/SelectMenu: show falsy label when model value is falsy","2025-09-08T12:42:34Z","https://github.com/nuxt/ui/issues/4869",0.6477178,{"description":3218,"labels":3219,"number":3222,"owner":3155,"repository":3156,"state":3212,"title":3223,"updated_at":3224,"url":3225,"score":3226},"### Environment\n\n- Operating System: Linux\n- Node Version: v20.12.0\n- Nuxt Version: -\n- CLI Version: 3.27.0\n- Nitro Version: -\n- Package Manager: pnpm@8.15.6\n- Builder: -\n- User Config: -\n- Runtime Modules: -\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nVue, Nuxt probably too\n\n### Version\n\nv3.3.0\n\n### Reproduction\n\nhttps://codesandbox.io/p/devbox/autumn-fog-8l524s\n\n### Description\n\nWhen nesting `Select` or `InputMenu` inside a `FormField`, clicking the label does not focus/open the input. Interestingly, it does work as expected for `SelectMenu`. See reproduction for examples.\n",[3220,3221],{"name":3146,"color":3147},{"name":3149,"color":3150},4690,"[Select/InputMenu]: Focus via label not working inside FormField","2025-08-14T10:22:07Z","https://github.com/nuxt/ui/issues/4690",0.65406066,{"description":3228,"labels":3229,"number":3233,"owner":3155,"repository":3156,"state":3212,"title":3234,"updated_at":3235,"url":3236,"score":3237},"### Environment\n\n- Operating System: `Darwin`\n- Node Version: `v22.14.0`\n- Nuxt Version: `4.0.3`\n- CLI Version: `3.28.0`\n- Nitro Version: `2.12.4`\n- Package Manager: `pnpm@10.9.0`\n- Builder: `-`\n- User Config: `compatibilityDate`, `devtools`, `extends`, `components`, `alias`, `dir`, `ssr`, `modules`, `ui`, `css`, `imports`, `app`, `runtimeConfig`\n- Runtime Modules: `@nuxt/ui@3.3.2`, `@pinia/nuxt@0.11.2`, `@vueuse/nuxt@13.6.0`\n- Build Modules: `-`\n\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.3.2\n\n### Reproduction\n\nhttps://codesandbox.io/p/devbox/fancy-leaf-5z2y85\n\n### Description\n\nThe InputMenu component crashes when provided with numeric values in its items prop, the same usage works correctly with SelectMenu.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3230,3231,3232],{"name":3146,"color":3147},{"name":3149,"color":3150},{"name":3152,"color":3153},4767,"InputMenu crashes when using numeric items","2025-08-16T02:41:48Z","https://github.com/nuxt/ui/issues/4767",0.6589536,{"description":3239,"labels":3240,"number":3246,"owner":3155,"repository":3156,"state":3212,"title":3247,"updated_at":3248,"url":3249,"score":3250},"### Environment\n\n- Operating System: `Windows_NT`\n- Node Version: `v22.14.0`\n- Nuxt Version: `3.17.5`\n- CLI Version: `3.25.1`\n- Nitro Version: `2.11.12`\n- Package Manager: `npm@10.9.2`\n- Builder: `-`\n- User Config: `compatibilityDate`, `devtools`, `srcDir`, `routeRules`, `app`, `svgSprite`, `alias`, `css`, `imports`, `modules`, `ssr`, `runtimeConfig`\n- Runtime Modules: `@nuxt/eslint@1.4.1`, `@nuxt/fonts@0.11.4`, `@nuxt/icon@1.14.0`, `@nuxt/image@1.10.0`, `@nuxt/scripts@0.11.8`, `@nuxt/test-utils@3.19.1`, `@nuxt/ui@3.1.3`, `@nuxtjs/svg-sprite@1.0.2`\n- Build Modules: `-`\n\n\n### Is this bug related to Nuxt or Vue?\n\n\nNuxt\n\n### Version\n\nv3.2.0\n\n### Reproduction\n\nhttps://codesandbox.io/p/devbox/dreamy-euler-9595k7\n\n\n### Description\n\n\n\nHi when i select copy payment id i got that error when i console log the row it gives me undefined upon clicking kindly check this link: https://ui.nuxt.com/components/table#with-context-menu\n\n#4259 \n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3241,3242,3245],{"name":3146,"color":3147},{"name":3243,"color":3244},"needs reproduction","CB47CF",{"name":3149,"color":3150},4452,"UTable context menu error during selection of items","2025-07-13T16:34:46Z","https://github.com/nuxt/ui/issues/4452",0.6637485,{"description":3252,"labels":3253,"number":3256,"owner":3155,"repository":3156,"state":3212,"title":3257,"updated_at":3258,"url":3259,"score":3260},"### Environment\n\n- Operating System: Windows_NT\n- Node Version: v24.2.0\n- Nuxt Version: 4.0.3\n- CLI Version: 3.28.0\n- Nitro Version: 2.12.4\n- Package Manager: bun@1.2.17\n- Builder: -\n- User Config: css, modules, nitro, i18n, imports, runtimeConfig, icon, compatibilityDate\n- Runtime Modules: @nuxtjs/i18n@10.0.6, @nuxt/ui-pro@3.3.1, @nuxt/eslint@1.9.0, @nuxtjs/html-validator@2.1.0, @nuxt/image@1.11.0, @vueuse/nuxt@13.7.0, @artmizu/nuxt-prometheus@2.5.2, @nuxtjs/seo@3.1.0\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.3.1\n\n### Reproduction\n\n```vue\n\u003Cscript lang=\"ts\" setup>\nconst value = ref(\"\");\nconst items: Array\u003Cstring | number> = [1, \"2\", 3];\n\u003C/script>\n\n\u003Ctemplate>\n \u003CUForm :state=\"value\" class=\"flex max-w-72 flex-col space-y-4 py-8\">\n \u003CUFormField label=\"UInputMenu\">\n \u003CUInputMenu v-model=\"value\" :items placeholder=\"UInputMenu\" />\n \u003C/UFormField>\n \u003CUFormField label=\"USelect\">\n \u003CUSelect v-model=\"value\" :items placeholder=\"USelect\" />\n \u003C/UFormField>\n \u003CUFormField label=\"USelectMenu\">\n \u003CUSelectMenu v-model=\"value\" :items placeholder=\"USelectMenu\" />\n \u003C/UFormField>\n \u003C/UForm>\n\u003C/template>\n```\n\n### Description\n\nAfter updating to version 3.3.1, the InputMenu, Select and SelectMenu component's placeholder value is not shown, if the value is not found in the items array. In version 3.3.0 the placeholder correctly shows up.\n\nNuxt UI 3.3.0\n\u003Cimg width=\"350\" height=\"300\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/2b0937d4-7640-4277-8169-ff192bc01d97\" />\n\nNuxt UI 3.3.1\n\u003Cimg width=\"410\" height=\"285\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/3d744e11-748b-4b3c-a236-fcee8fdcd765\" />\n\n\u003Cimg width=\"395\" height=\"298\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/ac7be307-ca5c-4957-a2fb-5721eebdea07\" />\n\nIf the v-model is `undefined` it works just like in 3.3.0, however in my projects I feel like that's not always achievable because of type definitions.\nI know I could set the default value to one of the items' values, but what if I don't want to populate the component by default and just show the placeholder? \nFor this to work in version 3.3.1 I'd have to loosen up the type definitions, so that required fields are not required anymore, which is wrong and I don't feel like I should have to do to keep the behavior of a UI component. \n\nShouldn't we have an exception for falsy values that are sometimes used as default values (empty string, 0...), so the placeholder can be shown without having to explicitly have `undefined` as the default value?\n\n### Additional context\n\nI haven't dug that deep, but I think #4689 introduced this behavior to these components. \n\n### Logs\n\n```shell-script\n\n```",[3254,3255],{"name":3146,"color":3147},{"name":3149,"color":3150},4812,"[InputMenu,Select,SelectMenu] Placeholder not showing in v3.3.1, if item is not found and default value is not undefined or null","2025-08-27T14:42:51Z","https://github.com/nuxt/ui/issues/4812",0.6652754,["Reactive",3262],{},["Set"],["ShallowReactive",3265],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fhb90WvkeD0aA4D3rOjXDb76OvoX4_7aYWxZRoDE13s4":-1},"/nuxt/ui/4627"]