\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```",[3170,3171],{"name":3154,"color":3155},{"name":3172,"color":3173},"v3","49DCB8",4139,"USelectMenu should emit 'change' after creating an item","2025-05-13T09:15:02Z","https://github.com/nuxt/ui/issues/4139",0.72181827,{"description":3180,"labels":3181,"number":3186,"owner":3160,"repository":3161,"state":3162,"title":3187,"updated_at":3188,"url":3189,"score":3190},"### 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!",[3182,3185],{"name":3183,"color":3184},"question","d876e3",{"name":3172,"color":3173},4859,"InputMenu behaves like a SelectMenu instead of a true input – needs proper input behavior","2025-09-10T22:12:11Z","https://github.com/nuxt/ui/issues/4859",0.7258457,{"description":3192,"labels":3193,"number":3197,"owner":3160,"repository":3161,"state":3162,"title":3198,"updated_at":3199,"url":3200,"score":3201},"### Description\n\nWhen using `multiple` with `USelectMenu` selected items can be deselected again. But when not having `multipe` option this is not the case. The select goes from undefined to a value and then can never become undefined again (without an external button).\n\nI would propose to add a new prop that allows values to be deselected, so the model becomes undefined again.\n\n### Additional context\n\n_No response_",[3194,3195,3196],{"name":3154,"color":3155},{"name":3172,"color":3173},{"name":3157,"color":3158},4647,"`USelectMenu`: Allow deselection of items","2025-08-02T13:00:23Z","https://github.com/nuxt/ui/issues/4647",0.7562652,{"description":3203,"labels":3204,"number":3208,"owner":3160,"repository":3161,"state":3162,"title":3209,"updated_at":3210,"url":3211,"score":3212},"### Description\n\nThis feature request proposes that the InputNumber component be enhanced with leading and trailing slot support. \n\nCurrently, components such as **Input**, **InputMenu**, **Select**, and **SelectMenu** already offer these slots for inserting custom content. For consistency across the UI library and to provide developers with a uniform customization experience, it is imperative that InputNumber is updated to include both leading and trailing slots. \n\n### Additional context\n\n_No response_",[3205,3206,3207],{"name":3154,"color":3155},{"name":3172,"color":3173},{"name":3157,"color":3158},4201,"[InputNumber] Add support for leading & trailing slots","2025-05-21T13:07:28Z","https://github.com/nuxt/ui/issues/4201",0.7636425,{"description":3214,"labels":3215,"number":3221,"owner":3160,"repository":3161,"state":3162,"title":3222,"updated_at":3223,"url":3224,"score":3225},"### 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```",[3216,3219,3220],{"name":3217,"color":3218},"bug","d73a4a",{"name":3172,"color":3173},{"name":3157,"color":3158},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.7639521,{"description":3227,"labels":3228,"number":3232,"owner":3160,"repository":3161,"state":3162,"title":3233,"updated_at":3234,"url":3235,"score":3236},"### Description\n\nThe RekaUI Combobox which is used for the InputMenu has a Cancel component which is not implemented in InputMenu. It clears the selection, and makes the field clear for a new search.\nI would like to suggest to implement this too as it enhances the usability with long lists as it allows for quicker search instead of scrolling a long list.\n\nLink to the Cancel component: https://reka-ui.com/docs/components/combobox#cancel\n\n### Additional context\n\n_No response_",[3229,3230,3231],{"name":3154,"color":3155},{"name":3172,"color":3173},{"name":3157,"color":3158},4239,"InputMenu: implement clear/cancel like in Reka UI combobox","2025-05-28T06:25:43Z","https://github.com/nuxt/ui/issues/4239",0.765386,{"description":3238,"labels":3239,"number":3242,"owner":3160,"repository":3161,"state":3162,"title":3243,"updated_at":3244,"url":3245,"score":3246},"### Description\n\nHi 👋 \n\nthe DropdownMenu component comes with some keyboard interactions, which is great. But I would like to control which keyboard interactions are enabled. I know this is handled by Reka, but I still wonder if it can be implemented/configured through the UDropdownMenu. Especially the Typeahead Search?\n\nExample:\n\nWe have an UInput in the #content-top slot and the results in the #item slot, when I type \"a\", then get results, then press \"a\" again the focus switches to the first result with the letter \"a\". Right now its possible to intercept the event on keydown for example, but I would rather just deactivate this feature.\n\n```\n\u003CUDropdownMenu :items mode=\"click\">\n \u003CUButton>Trigger\u003C/UButton>\n\n \u003Ctemplate #content-top>\n \u003CUInput v-model=\"search\" placeholder=\"Search\" />\n \u003C/template>\n\n \u003Ctemplate #item=\"{ item }\">\n \u003Cspan v-text=\"item.label\" />\n \u003C/template>\n\u003C/UDropdownMenu>\n```",[3240,3241],{"name":3183,"color":3184},{"name":3172,"color":3173},4636,"DropdownMenu keyboard interaction handling","2025-07-31T06:44:47Z","https://github.com/nuxt/ui/issues/4636",0.77000326,{"description":3248,"labels":3249,"number":3252,"owner":3160,"repository":3161,"state":3253,"title":3254,"updated_at":3255,"url":3256,"score":3257},"### For what version of Nuxt UI are you suggesting this?\n\nv2.x\n\n### Description\n\nCurrently, we are unable to manually trigger the searchable method. Lets assume i have one `USelectMenu` component that list all `Parent` object and a second `USelectMenu` that list all `Children` of the selected `Parent`. Currently, when the `USelectMenu` component i mounted, the search query is executed even if the parent object is not yet selected.\n\nIt would me very useful to be able to manually trigger the search query method to populate the `USelectMenu` options.\n\nIs there any alternative to do it using the current behavior ? Maybe using a `ref` or something ?\n\n### Additional context\n\n_No response_",[3250,3251],{"name":3154,"color":3155},{"name":3157,"color":3158},2882,"closed","USelectMenu: Manually trigger the search query","2025-05-10T17:19:44Z","https://github.com/nuxt/ui/issues/2882",0.73412967,{"description":3259,"labels":3260,"number":3266,"owner":3160,"repository":3161,"state":3253,"title":3267,"updated_at":3268,"url":3269,"score":3270},"### Environment\n\n- Operating System: Darwin\n- Node Version: v22.14.0\n- Nuxt Version: 3.17.4\n- CLI Version: 3.25.1\n- Nitro Version: 2.11.12\n- Package Manager: pnpm@10.11.0\n- Builder: -\n- User Config: modules, devtools, css, ui, runtimeConfig, compatibilityDate, dayjs, eslint, image, sanity, supabase\n- Runtime Modules: @nuxt/eslint@1.4.1, @nuxt/ui@3.1.3, @nuxt/image@1.10.0, @nuxtjs/sanity@1.13.3, @nuxtjs/supabase@1.5.1, motion-v/nuxt@0.11.3, dayjs-nuxt@2.1.11, @pinia/nuxt@0.10.1\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.17.4\n\n### Reproduction\n\nHappens also in the Nuxt UI documentation: https://ui.nuxt.com/components/input-menu#items\n\n\n\n### Description\n\nI would expect that all list items appear on the first opening and not on the second one like in following video:\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3261,3262,3265],{"name":3217,"color":3218},{"name":3263,"color":3264},"duplicate","cfd3d7",{"name":3172,"color":3173},4240,"InputMenu shows only seleceted value in the list on first opening","2025-05-28T08:08:48Z","https://github.com/nuxt/ui/issues/4240",0.7430726,["Reactive",3272],{},["Set"],["ShallowReactive",3275],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fIZlCxMYBUYFckusi1yafZKNxMOV-imUSg88Qwv8d7Wg":-1},"/nuxt/ui/4106"]