\n\u003C/template>\n```\n\nI think created items should emit `change` so we can validate them properly.\n\nAdditionally, because of https://github.com/nuxt/ui/issues/3736,the field always starts in an error state when a new item is created in certain conditions (regardless of whether the item meets the schema's requirements or not).\n\n------\n\nCurrent workaround is to run the validation manaully on a field after mutating the model:\n\n```ts\nasync function onCreate(item: string) {\n selected.value = item\n\n await formRef.value?.validate({ name: 'fieldName' })\n}\n```",[3139,3142],{"name":3140,"color":3141},"enhancement","a2eeef",{"name":3143,"color":3144},"v3","49DCB8",4139,"nuxt","ui","open","USelectMenu should emit 'change' after creating an item","2025-05-13T09:15:02Z","https://github.com/nuxt/ui/issues/4139",0.63475555,{"description":3154,"labels":3155,"number":3162,"owner":3146,"repository":3147,"state":3148,"title":3163,"updated_at":3164,"url":3165,"score":3166},"### Environment\n\n- OS: Windows\n- Nuxt: v4.0.3\n- Node: v22.14.0\n\n### Version\n\nv4.0.3\n\n### Reproduction\n\nhttps://stackblitz.com/edit/nuxt-ui-gtu8vgxz?file=app.vue\n\n### Description\n\nThe USelectMenu component does not block form validation even when setting the required prop.\nI though this was a bug since the USelect component instead correctly blocks validation when setting the required prop.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3156,3159],{"name":3157,"color":3158},"bug","d73a4a",{"name":3160,"color":3161},"triage","ffffff",4757,"USelectMenu required prop is not blocking form validation","2025-08-15T10:52:46Z","https://github.com/nuxt/ui/issues/4757",0.639178,{"description":3168,"labels":3169,"number":3173,"owner":3146,"repository":3147,"state":3148,"title":3174,"updated_at":3175,"url":3176,"score":3177},"### 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```",[3170,3171,3172],{"name":3157,"color":3158},{"name":3143,"color":3144},{"name":3160,"color":3161},4664,"InputMenu emit order","2025-09-08T15:55:07Z","https://github.com/nuxt/ui/issues/4664",0.6859362,{"description":3179,"labels":3180,"number":3184,"owner":3146,"repository":3147,"state":3148,"title":3185,"updated_at":3186,"url":3187,"score":3188},"### 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```",[3181,3182,3183],{"name":3157,"color":3158},{"name":3143,"color":3144},{"name":3160,"color":3161},4839,"Slideover does not work when called from DropdownMenu","2025-09-01T06:45:41Z","https://github.com/nuxt/ui/issues/4839",0.69141954,{"description":3190,"labels":3191,"number":3195,"owner":3146,"repository":3147,"state":3148,"title":3196,"updated_at":3197,"url":3198,"score":3199},"### Environment\n\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.1\n- Build Modules: -\n------------------------------\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.17.3\n\n### Reproduction\n\nhttps://codesandbox.io/p/devbox/zen-albattani-93gcyn\n\nType `COMPLETE` into the input menu and press enter. `DROPOFF_COMPLETE` becomes selected\n\n### Description\n\nIf I type an exact match for one of the items into the InputMenu and press Enter, I would expect that item to be selected.\n\nHowever, in certain cases when other items are a superset of the search text, those become selected.\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3192,3193,3194],{"name":3157,"color":3158},{"name":3143,"color":3144},{"name":3160,"color":3161},4672,"InputMenu sometimes chooses alternate option even when exact match to one option is typed","2025-08-06T20:48:15Z","https://github.com/nuxt/ui/issues/4672",0.6938782,{"description":3201,"labels":3202,"number":3207,"owner":3146,"repository":3147,"state":3148,"title":3208,"updated_at":3209,"url":3210,"score":3211},"### Package\n\nv3.18\n\n### Description\n\nHello,\nI've been using Nuxt UI for many months and I really love it!\n\nHowever, I've often run into limitations with the `InputMenu` component, because its behavior feels too close to the `SelectMenu`.\n\nThe main difference (at least for me) is that since it's an **input**, the priority should be the input value itself. But currently, it behaves more like the `SelectMenu`, where the value must exist in the provided `:items` in order to be set. The text entered in the field is only treated as a **search term**, and it is not updated in the bound **ref** — while it should be, since this is supposed to be an **input**.\n\nI think the `InputMenu` should allow any value typed by the user to be stored and displayed, even if it’s not present in the `:items` list. This would make it much more flexible and closer to the expected behavior of an **input** field.\n\nFor example, in this `InputMenu` example, if i start to type 'Hello', the **ref** value still remains 'Backlog'... \nThis is the excepted behaviour for a `SelectMenu`, but for a `InputMenu`, the **ref** value should become 'Hello':\n\n\u003Cimg width=\"583\" height=\"308\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/7fd4d063-310b-4556-a61a-20c962a4785a\" />\n\nAnd for me the `:create-item` option doesn’t solve this case, because from a UX perspective it doesn’t behave like a true **input**. The **input** value shouldn’t require extra steps to be reflected in the bound **ref**.\n\nI'm curious about your point of view, and if you agree with me, \nwould it be possible to adjust this behavior, or at least provide an option to allow free input values?\n\nThanks a lot for your work!",[3203,3206],{"name":3204,"color":3205},"question","d876e3",{"name":3143,"color":3144},4859,"InputMenu behavior too close to SelectMenu – Option needed to behave like a true input","2025-09-01T10:11:44Z","https://github.com/nuxt/ui/issues/4859",0.6946963,{"description":3213,"labels":3214,"number":3218,"owner":3146,"repository":3147,"state":3219,"title":3220,"updated_at":3221,"url":3222,"score":3223},"### Environment\n\n------------------------------\n- Operating System: Darwin\n- Node Version: v22.13.0\n- Nuxt Version: 3.16.1\n- CLI Version: 3.23.1\n- Nitro Version: 2.11.7\n- Package Manager: bun@1.2.4\n- Builder: -\n- User Config: compatibilityDate, devtools, runtimeConfig, nitro, routeRules, modules, ui, supabase, site, feed, sitemap, robots, schemaOrg, image, hub\n- Runtime Modules: @nuxt/ui@3.0.1, @nuxtjs/supabase@1.5.0, @vueuse/nuxt@13.0.0, @nuxt/image@1.10.0, @nuxthub/core@0.8.18, @nuxtjs/sitemap@7.2.9, nuxt-module-feed@1.1.4, @nuxtjs/robots@5.2.8, nuxt-schema-org@5.0.4, nuxt-link-checker@4.3.0\n- Build Modules: -\n------------------------------\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/adoring-gates-fd8q9s\n\n### Description\n\n## Expected behaviour\nValidation should trigger when a user adds or removes items from an input menu that has the `multiple` prop\n\n## Actual behaviour\nValidation seems to trigger when the input menu is opened or closed, but not when items are removed\n\n## Reproduction\n1. Use the codesandbox provided\n2. Add all 4 items to the input\n3. Validation should trigger saying 3 max\n4. Remove an item\n5. **Validation error persists, when it should be gone**\n6. Remove all the items\n7. Add a single item\n8. Remove them item\n9. **Validation error should appear stating 1 item min, but it doesn't**\n\n### Additional context\n\n## Screen capture\n\nhttps://github.com/user-attachments/assets/fccda9b1-2837-4b7d-85ad-5d63480582a1\n\n### Logs\n\n```shell-script\n\n```",[3215,3216,3217],{"name":3157,"color":3158},{"name":3143,"color":3144},{"name":3160,"color":3161},3726,"closed","Form validation with InputMenu doesn't trigger when expected","2025-04-08T19:48:00Z","https://github.com/nuxt/ui/issues/3726",0.6424647,{"description":3225,"labels":3226,"number":3230,"owner":3146,"repository":3147,"state":3219,"title":3231,"updated_at":3232,"url":3233,"score":3234},"### Environment\n\n- Operating System: `Darwin`\n- Node Version: `v22.13.0`\n- Nuxt Version: `3.16.2`\n- CLI Version: `3.24.1`\n- Nitro Version: `2.11.9`\n- Package Manager: `pnpm@10.8.1`\n- Builder: `-`\n- User Config: `modules`, `devtools`, `css`, `site`, `future`, `compatibilityDate`, `echarts`, `eslint`, `fonts`, `icon`, `sitemap`\n- Runtime Modules: `@nuxtjs/sitemap@7.2.10`, `@nuxt/content@3.4.0`, `@nuxt/eslint@1.3.0`, `@nuxt/ui-pro@3.0.2`, `@vueuse/nuxt@13.1.0`, `nuxt-echarts@0.3.0`\n- Build Modules: `-`\n\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.0.2\n\n### Reproduction\n\nhttps://codesandbox.io/p/devbox/peaceful-elbakyan-3ddsxd\n\n### Description\n\nMy understanding is that the onSelect event of SelectMenu should be consistent with the DropdownMenu component, but in reality, it is not.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3227,3228,3229],{"name":3157,"color":3158},{"name":3143,"color":3144},{"name":3160,"color":3161},3978,"The onSelect event of the SelectMenu component was not triggered","2025-05-05T15:20:55Z","https://github.com/nuxt/ui/issues/3978",0.6495051,{"description":3236,"labels":3237,"number":3247,"owner":3146,"repository":3147,"state":3219,"title":3248,"updated_at":3249,"url":3250,"score":3251},"### Environment\n\nNuxt project info: (copied to clipboard) nuxi 10:36:44\n\n------------------------------\n- Operating System: Windows_NT\n- Node Version: v20.9.0\n- Nuxt Version: 3.16.0\n- CLI Version: 3.25.0\n- Nitro Version: 2.11.11\n- Package Manager: npm@10.9.0\n- Builder: -\n- User Config: devtools, modules, css, future, compatibilityDate, experimental, nitro, sourcemap, ssr, spaLoadingTemplate, runtimeConfig\n- Runtime Modules: @nuxt/ui@3.1.1, @nuxtjs/mdc@0.15.0, @vueuse/nuxt@13.1.0\n- Build Modules: -\n------------------------------\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.1.1\n\n### Reproduction\n\n\nInput Menu Send an event when using @Change\n\n\n\nBut it is scheduled to send a value and this generates the error in console\n\n\n\n\n\n### Description\n\nhttps://github.com/user-attachments/assets/3fdd5798-3f77-45e0-a86b-18a2195219f2\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3238,3239,3242,3243,3244],{"name":3157,"color":3158},{"name":3240,"color":3241},"needs reproduction","CB47CF",{"name":3143,"color":3144},{"name":3160,"color":3161},{"name":3245,"color":3246},"closed-by-bot","ededed",4103,"InputMenu Event onChange","2025-05-17T02:08:14Z","https://github.com/nuxt/ui/issues/4103",0.66421723,{"description":3253,"labels":3254,"number":3257,"owner":3146,"repository":3147,"state":3219,"title":3258,"updated_at":3259,"url":3260,"score":3261},"### 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```",[3255,3256],{"name":3157,"color":3158},{"name":3143,"color":3144},4869,"InputMenu/Select/SelectMenu: show falsy label when model value is falsy","2025-09-08T12:42:34Z","https://github.com/nuxt/ui/issues/4869",0.6706776,["Reactive",3263],{},["Set"],["ShallowReactive",3266],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fqKbVY_Yx5d-Z9gw1dI4DRNmMoNws3RIesFzRqhI_97U":-1},"/nuxt/ui/3736"]