\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!",[3139,3142],{"name":3140,"color":3141},"question","d876e3",{"name":3143,"color":3144},"v3","49DCB8",4859,"nuxt","ui","open","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.722855,{"description":3154,"labels":3155,"number":3163,"owner":3146,"repository":3147,"state":3148,"title":3164,"updated_at":3165,"url":3166,"score":3167},"### 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```",[3156,3159,3160],{"name":3157,"color":3158},"bug","d73a4a",{"name":3143,"color":3144},{"name":3161,"color":3162},"triage","ffffff",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.7236703,{"description":3169,"labels":3170,"number":3176,"owner":3146,"repository":3147,"state":3148,"title":3177,"updated_at":3178,"url":3179,"score":3180},"### 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_",[3171,3174,3175],{"name":3172,"color":3173},"enhancement","a2eeef",{"name":3143,"color":3144},{"name":3161,"color":3162},4647,"`USelectMenu`: Allow deselection of items","2025-08-02T13:00:23Z","https://github.com/nuxt/ui/issues/4647",0.7324144,{"description":3182,"labels":3183,"number":3186,"owner":3146,"repository":3147,"state":3148,"title":3187,"updated_at":3188,"url":3189,"score":3190},"### Description\n\nDear Contributors,\n\nNuxtUI has been a great help in my app development. Thank you very much.\n\nI would like to request the addition of a new feature. I would appreciate your consideration.\n\n\nCommon search engines provide a search bar with a suggestion feature.\nSelecting a keyword from the provided suggestions is optional; if a user does not select a suggestion, the content they have entered takes precedence.\n\nHowever, the current InputMenu specifications automatically select the first item on the list if the user doesn't make a selection, overwriting the user's input with that value.\nIt would be useful if there were a feature that limited the overwriting of user input to only cases where the user explicitly selects an item from the list.\n\nThank you.\n\n### Additional context\n\n_No response_",[3184,3185],{"name":3172,"color":3173},{"name":3161,"color":3162},4717,"InputMenu want to selection to optional","2025-08-12T05:38:55Z","https://github.com/nuxt/ui/issues/4717",0.7339991,{"description":3192,"labels":3193,"number":3197,"owner":3146,"repository":3147,"state":3198,"title":3199,"updated_at":3200,"url":3201,"score":3202},"### Version\n\nLatest commit https://pkg.pr.new/@nuxt/ui@62ab016\n\n### Description\n\nWhen fetching items using [ignore-filter prop ](https://ui.nuxt.com/components/select-menu#with-ignore-filter) `\u003CUSelectMenu>` does not remember the current selection.\n\nCurrently it works only if the selected item stays in the items array which is barely the case if dealing with more than 10 items:\n\nhttps://github.com/user-attachments/assets/f5c6b264-52a5-4d8b-b015-242e36d91fdb\n\nThis happens in two cases:\n\n1. When selecting an item the searchTerm gets resetted, the items-array changes and the selected item is no more in it -> Select menu label becomes empty\n2. When an item is selected, but searching for other items that dont include seleced item -> Select menu label becomes empty\n\n### Reproduction\n\nAlso reproducable in the docs:\nhttps://ui.nuxt.com/components/select-menu#with-ignore-filter\n\nhttps://github.com/user-attachments/assets/ec3065bb-7cc2-4976-9dde-da99dd2311b6\n\nHere case 1 never happens because the jsonplaceholder-api only has just 5 user-items so the selected user is always in the default empty search result. BUT case 2 happens: Select a user, open select again, type in any other name that doesnt include first user -> Select menu label becomes empty (weirdly tho, the avatar stays)",[3194,3195,3196],{"name":3157,"color":3158},{"name":3143,"color":3144},{"name":3161,"color":3162},4582,"closed","SelectMenu with fetched items (ignore-filter) doesnt remember current selection","2025-08-14T09:04:53Z","https://github.com/nuxt/ui/issues/4582",0.6960903,{"description":3204,"labels":3205,"number":3211,"owner":3146,"repository":3147,"state":3198,"title":3212,"updated_at":3213,"url":3214,"score":3215},"### Environment\n\nNuxt UI pro v 3.1.0\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.1.0\n\n### Reproduction\n\nhttps://ui.nuxt.com/components/input-menu#control-search-term\n\n### Description\n\nHello, \n\nI am reopening an issue based on https://github.com/nuxt/ui/issues/3782\n\nI still have an issue on the InputMenu that filters with the default value.\n\nAs a reproduction : we can see the same behavior I am facing in the documentation : https://ui.nuxt.com/components/input-menu#control-search-term . \n\n1) => The first click on InputMenu shows only the seacherd term (here Backlog)\n2) => If I close the popover and reopen it a second time, it shows the entire list.\n\nI tried the :reset-search-term-on-select=\"false\" , it allows to display the entire list at 1st click but it leads to not showing the default selected value (the placeholder is displayed).\n\nActually, I am looking to display the entire list at first click, even if a value is already selected.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3206,3207,3208],{"name":3157,"color":3158},{"name":3143,"color":3144},{"name":3209,"color":3210},"reka-ui","56d799",3993,"InputMenu Clear Search on Select at first click","2025-07-16T10:57:06Z","https://github.com/nuxt/ui/issues/3993",0.7087272,{"description":3217,"labels":3218,"number":3224,"owner":3146,"repository":3147,"state":3198,"title":3225,"updated_at":3226,"url":3227,"score":3228},"### 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```",[3219,3220,3223],{"name":3157,"color":3158},{"name":3221,"color":3222},"duplicate","cfd3d7",{"name":3143,"color":3144},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.7109729,{"description":3230,"labels":3231,"number":3235,"owner":3146,"repository":3146,"state":3198,"title":3236,"updated_at":3237,"url":3238,"score":3239},"### Environment\n\n------------------------------\r\n- Operating System: Linux\r\n- Node Version: v20.14.0\r\n- Nuxt Version: 3.12.4\r\n- CLI Version: 3.12.0\r\n- Nitro Version: 2.9.7\r\n- Package Manager: pnpm@9.7.1\r\n- Builder: -\r\n- User Config: runtimeConfig, extends, modules, ui, colorMode, routeRules, devtools, typescript, future, eslint, nitro, i18n, compatibilityDate\r\n- Runtime Modules: @nuxt/eslint@0.5.0, @nuxt/fonts@0.7.1, @nuxt/ui@2.18.4, @vueuse/nuxt@10.11.0, @nuxtjs/i18n@8.5.0\r\n- Build Modules: -\r\n------------------------------\r\n\n\n### Reproduction\n\nhttps://stackblitz.com/edit/nuxt-ui-u6tm1b?file=app.vue\n\n### Describe the bug\n\nWhen using a `v-model` prop with some initial object values (such as fetched already selected data from backend), the `\u003CUSelectMenu>` component doesn't show these as selected and seems to ignore them completely.\r\n\r\nEven when selecting the same objects again, it just seems to add them to the array and disregard anything, that was there previously.\n\n### Additional context\n\nThe behaviour changes when setting the `by` prop. In my case, I set it to `id`, after which I can see the object as selected, **but only** in the dropdown.\r\nThe button itself still shows `0 selected`.\n\n### Logs\n\n_No response_",[3232],{"name":3233,"color":3234},"pending triage","E99695",28733,"SelectMenu initial object values","2024-08-28T03:27:34Z","https://github.com/nuxt/nuxt/issues/28733",0.728311,{"description":3241,"labels":3242,"number":3246,"owner":3146,"repository":3146,"state":3198,"title":3247,"updated_at":3248,"url":3249,"score":3250},"Hi,\r\ni have problem with index page not rendered correctly when i access it directly (not from some other page). I am fetching data asynchronously and further i am using that data in three different components on the page. If I comment two of them page will be rendered correctly but as soon as I add another component (that was previously commented) the page breaks. Please refer to [this issue](https://github.com/nuxt/nuxt.js/issues/1185). [This is reproduction repo](https://github.com/dinokajtez/nuxt-js-reproduction) created as it was required by reviewer.\n\n\u003C!--cmty-->\u003C!--cmty_prevent_hook-->\n\u003Cdiv align=\"right\">\u003Csub>\u003Cem>This question is available on \u003Ca href=\"https://nuxtjs.cmty.io\">Nuxt.js\u003C/a> community (\u003Ca href=\"https://nuxtjs.cmty.io/nuxt/nuxt.js/issues/c1066\">#c1066\u003C/a>)\u003C/em>\u003C/sub>\u003C/div>",[3243],{"name":3244,"color":3245},"2.x","d4c5f9",1208,"Multiple components not rendered with async data as props (reopened)","2023-01-18T15:40:55Z","https://github.com/nuxt/nuxt/issues/1208",0.7320214,{"description":3252,"labels":3253,"number":3257,"owner":3146,"repository":3147,"state":3198,"title":3258,"updated_at":3259,"url":3260,"score":3261},"### Description\n\nNeed to have the ability to provide a callback function to onRemoveTag when selecting multiple items to be able to customize its behavior.\n\n### Additional context\n\nIn my use case for example I have an InputMenu with Multiple selections the items list contains values that fall under multiple categories for example A, B, and C with the ability to search for any of them in the same InputMenu, so the list of items looks something like this:\n- A: A1\n- A: A2\n- B: B5\n- C: C7\nthe state is then stored in a pinia store based on the category onSelect, e.g. `if (key == \"A\") store.listA.push(item.value)` when I click on the remove tag the v-model value is updated, but I have no idea which category was it from, meaning I will have to check all the items to know which state to update since they are actually separate.",[3254,3255,3256],{"name":3172,"color":3173},{"name":3143,"color":3144},{"name":3161,"color":3162},4463,"[InputMenu] ability to control behavior of onRemoveTag","2025-07-16T20:28:46Z","https://github.com/nuxt/ui/issues/4463",0.7345596,["Reactive",3263],{},["Set"],["ShallowReactive",3266],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fXdCs9SEC-O4FyvjrO69yesjYHe6Ohgvs3p8K77Rw7Yw":-1},"/nuxt/ui/3348"]