\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```",[3020,3023],{"name":3021,"color":3022},"enhancement","a2eeef",{"name":3024,"color":3025},"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.72181827,{"description":3035,"labels":3036,"number":3042,"owner":3027,"repository":3028,"state":3029,"title":3043,"updated_at":3044,"url":3045,"score":3046},"### 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_",[3037,3038,3039],{"name":3021,"color":3022},{"name":3024,"color":3025},{"name":3040,"color":3041},"triage","ffffff",4201,"[InputNumber] Add support for leading & trailing slots","2025-05-21T13:07:28Z","https://github.com/nuxt/ui/issues/4201",0.7636425,{"description":3048,"labels":3049,"number":3053,"owner":3027,"repository":3028,"state":3029,"title":3054,"updated_at":3055,"url":3056,"score":3057},"### 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_",[3050,3051,3052],{"name":3021,"color":3022},{"name":3024,"color":3025},{"name":3040,"color":3041},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":3059,"labels":3060,"number":3065,"owner":3027,"repository":3028,"state":3029,"title":3066,"updated_at":3067,"url":3068,"score":3069},"### 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```",[3061,3064],{"name":3062,"color":3063},"question","d876e3",{"name":3024,"color":3025},4636,"DropdownMenu keyboard interaction handling","2025-07-31T06:44:47Z","https://github.com/nuxt/ui/issues/4636",0.77000326,{"description":3071,"labels":3072,"number":3081,"owner":3027,"repository":3027,"state":3029,"title":3082,"updated_at":3083,"url":3084,"score":3085},"### Describe the feature\r\n\r\nEspecially when it comes to handling URL state, I've seen the wildest implementations.\r\nIt would be great to have two simple helper composables which create \"reactive\" router params and router query values.\r\nThat way, it would be even easier to sync URL state (and we could properly document + advise it).\r\n\r\nThis [already exists in VueUse](https://vueuse.org/router/useRouteParams/) but does not utilize `navigateTo`.\r\n\r\nExample syntax (adapted from VueUse example)\r\n\r\n```ts\r\nconst search = useRouteQuery('search')\r\n\r\nconst otherSearch = useRouteQuery('search', 'foo') // default value\r\n\r\nconst page = useRouteQuery('page', '1', { transform: Number }) // with transform function too\r\n\r\nconsole.log(search.value) // same as route.query.search\r\nsearch.value = 'foobar' // Calls navigateTo({ query: { search: 'foobar' } }, { replace: true })\r\n```\r\n\r\n---\r\n\r\nRelated issue (was more bare-bone): https://github.com/nuxt/nuxt/issues/24365\r\n\r\n### Additional information\r\n\r\n- [X] Would you be willing to help implement this feature?\r\n- [X] Could this feature be implemented as a module?\r\n\r\n### Final checks\r\n\r\n- [X] Read the [contribution guide](https://nuxt.com/docs/community/contribution).\r\n- [X] Check existing [discussions](https://github.com/nuxt/nuxt/discussions) and [issues](https://github.com/nuxt/nuxt/issues).",[3073,3075,3078],{"name":3021,"color":3074},"8DEF37",{"name":3076,"color":3077},"workaround available","11376d",{"name":3079,"color":3080},"needs details","493824",24788,"`useRouteParams` and `useRouteQuery` for Nuxt","2024-09-13T10:57:55Z","https://github.com/nuxt/nuxt/issues/24788",0.77414924,{"description":3087,"labels":3088,"number":3091,"owner":3027,"repository":3028,"state":3092,"title":3093,"updated_at":3094,"url":3095,"score":3096},"### 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_",[3089,3090],{"name":3021,"color":3022},{"name":3040,"color":3041},2882,"closed","USelectMenu: Manually trigger the search query","2025-05-10T17:19:44Z","https://github.com/nuxt/ui/issues/2882",0.73412967,{"description":3098,"labels":3099,"number":3107,"owner":3027,"repository":3028,"state":3092,"title":3108,"updated_at":3109,"url":3110,"score":3111},"### 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```",[3100,3103,3106],{"name":3101,"color":3102},"bug","d73a4a",{"name":3104,"color":3105},"duplicate","cfd3d7",{"name":3024,"color":3025},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,{"description":3113,"labels":3114,"number":3118,"owner":3027,"repository":3028,"state":3092,"title":3119,"updated_at":3120,"url":3121,"score":3122},"### 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.",[3115,3116,3117],{"name":3021,"color":3022},{"name":3024,"color":3025},{"name":3040,"color":3041},4463,"[InputMenu] ability to control behavior of onRemoveTag","2025-07-16T20:28:46Z","https://github.com/nuxt/ui/issues/4463",0.74443173,{"description":3124,"labels":3125,"number":3129,"owner":3027,"repository":3028,"state":3092,"title":3130,"updated_at":3131,"url":3132,"score":3133},"### Description\n\nI would like to be able to focus on the input in an InputMenu using a keyboard shortcut. This is already possible for the UInput (https://ui.nuxt.com/components/input#with-keyboard-shortcut), but the focus function is not exposed for UInputMenu.\n\n```\nconst input = useTemplateRef('input')\n\ndefineShortcuts({\n '/': () => {\n input.value?.inputRef?.focus()\n }\n})\n```\n\n### Additional context\n\n_No response_",[3126,3127,3128],{"name":3021,"color":3022},{"name":3024,"color":3025},{"name":3040,"color":3041},4450,"UInputMenu focus with keyboard shortcut","2025-07-03T15:23:10Z","https://github.com/nuxt/ui/issues/4450",0.749749,{"description":3135,"labels":3136,"number":3142,"owner":3027,"repository":3028,"state":3092,"title":3143,"updated_at":3144,"url":3145,"score":3146},"### 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```",[3137,3138,3139],{"name":3101,"color":3102},{"name":3024,"color":3025},{"name":3140,"color":3141},"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.7517075,["Reactive",3148],{},["Set"],["ShallowReactive",3151],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fIZlCxMYBUYFckusi1yafZKNxMOV-imUSg88Qwv8d7Wg":-1},"/nuxt/ui/4106"]