\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```",[2856,2859],{"name":2857,"color":2858},"enhancement","a2eeef",{"name":2860,"color":2861},"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":2871,"labels":2872,"number":2880,"owner":2863,"repository":2864,"state":2865,"title":2881,"updated_at":2882,"url":2883,"score":2884},"### Environment\n\n- Operating System: Darwin\n- Node Version: v22.14.0\n- Nuxt Version: 3.16.2\n- CLI Version: 3.25.0\n- Nitro Version: 2.11.9\n- Package Manager: npm@10.9.2\n- Builder: -\n- User Config: ssr, devtools, modules, css, app, runtimeConfig, i18n, devServer, colorMode, compatibilityDate\n- Runtime Modules: @nuxt/ui@3.0.2, @pinia/nuxt@0.5.5, @nuxt/eslint@0.5.7, @nuxtjs/i18n@9.5.3, @nuxtjs/device@3.2.4\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\n3.0.2\n\n### Reproduction\n\nhttps://codesandbox.io/p/devbox/blazing-currying-smhzvr\nnew: https://codesandbox.io/p/devbox/nuxt-ui3-n3sxks\n\n### Description\n\nI have search input inside UDropdownMenu to search items:\n1. When I focus input then hover items input loosing focus\n2. When I start typing input loosing focus and items are getting focus. You can try in reproduction url.\n3. [Offtop] Also there should be slot for menu iteself \n\n### Additional context\n\nAs I said I'm trying to type \"t\" but not working at all. This should not work this way\n\nhttps://github.com/user-attachments/assets/6c684cdb-1d5d-48c8-a5e5-eacf8507f823\n\n### Logs\n\n```shell-script\n\n```",[2873,2876,2879],{"name":2874,"color":2875},"bug","d73a4a",{"name":2877,"color":2878},"needs reproduction","CB47CF",{"name":2860,"color":2861},4098,"Unable to use search input inside UDropdownMenu","2025-05-25T11:21:17Z","https://github.com/nuxt/ui/issues/4098",0.7610652,{"description":2886,"labels":2887,"number":2893,"owner":2863,"repository":2864,"state":2865,"title":2894,"updated_at":2895,"url":2896,"score":2897},"### 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_",[2888,2889,2890],{"name":2857,"color":2858},{"name":2860,"color":2861},{"name":2891,"color":2892},"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":2899,"labels":2900,"number":2904,"owner":2863,"repository":2864,"state":2865,"title":2905,"updated_at":2906,"url":2907,"score":2908},"### 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_",[2901,2902,2903],{"name":2857,"color":2858},{"name":2860,"color":2861},{"name":2891,"color":2892},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":2910,"labels":2911,"number":2920,"owner":2863,"repository":2863,"state":2865,"title":2921,"updated_at":2922,"url":2923,"score":2924},"### 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).",[2912,2914,2917],{"name":2857,"color":2913},"8DEF37",{"name":2915,"color":2916},"workaround available","11376d",{"name":2918,"color":2919},"needs details","493824",24788,"`useRouteParams` and `useRouteQuery` for Nuxt","2024-09-13T10:57:55Z","https://github.com/nuxt/nuxt/issues/24788",0.77414924,{"description":2926,"labels":2927,"number":2931,"owner":2863,"repository":2864,"state":2865,"title":2932,"updated_at":2933,"url":2934,"score":2935},"### Description\n\nHello,\n\nI've spent the last couple of hours trying to implement right-click functionality on UTable rows. I've reviewed existing issues but couldn't find a solution that fits this need.\n\nWhat I want to achieve is to show a UContextMenu with actions related to the clicked row when the user right-clicks on it.\n\nCurrently, there is no way I could find to detect right-click events on individual rows along with their row data. If UTable had a #row slot or a dedicated @click.right event that provides the clicked row’s data, this would be easily achievable.\n\nIf there is any workaround or method to implement this right-click behavior on rows with access to row data, I would really appreciate if someone could share it.\n\nThank you!\n\n\n\n### Additional context\n\n_No response_",[2928,2929,2930],{"name":2857,"color":2858},{"name":2860,"color":2861},{"name":2891,"color":2892},4259,"Add support for @click.right event on UTable rows to enable context menus","2025-05-30T14:35:19Z","https://github.com/nuxt/ui/issues/4259",0.78227615,{"description":2937,"labels":2938,"number":2941,"owner":2863,"repository":2864,"state":2942,"title":2943,"updated_at":2944,"url":2945,"score":2946},"### 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_",[2939,2940],{"name":2857,"color":2858},{"name":2891,"color":2892},2882,"closed","USelectMenu: Manually trigger the search query","2025-05-10T17:19:44Z","https://github.com/nuxt/ui/issues/2882",0.73412967,{"description":2948,"labels":2949,"number":2955,"owner":2863,"repository":2864,"state":2942,"title":2956,"updated_at":2957,"url":2958,"score":2959},"### 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```",[2950,2951,2954],{"name":2874,"color":2875},{"name":2952,"color":2953},"duplicate","cfd3d7",{"name":2860,"color":2861},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":2961,"labels":2962,"number":2967,"owner":2863,"repository":2864,"state":2942,"title":2968,"updated_at":2969,"url":2970,"score":2971},"### Description\n\nIt is possible add an slot named `option-append` which will be after the menu content?\r\nFor example it will be useful to add an intersection observer when creating an infinite scroll select.\n\n### Additional context\n\n_No response_",[2963,2964,2966],{"name":2857,"color":2858},{"name":2965,"color":2892},"wontfix-v2",{"name":2860,"color":2861},1167,"`USelectMenu` option-append","2025-05-23T15:24:34Z","https://github.com/nuxt/ui/issues/1167",0.7635108,{"description":2973,"labels":2974,"number":2978,"owner":2863,"repository":2863,"state":2942,"title":2979,"updated_at":2980,"url":2981,"score":2982},"I'm trying to create a very simple application. \r\nThat is: the page with the search box at the top and ~~search results below~~ nothing, just a box.\r\nWhen a user types something in the box, the url should be automatically updated. \r\nFor example, if a user types `something`, the url should become `/search?srch=something`.\r\nWhen a user reloads the `/search?srch=something`, the page should appear with `something` already typed in the input field. \r\n\r\nHere's the example, https://github.com/Kasheftin/nuxt-search-bug, and the relevant page from there: https://github.com/Kasheftin/nuxt-search-bug/blob/master/pages/search.vue\r\n\r\nSo I watch for the changes of the input field and call `this.$router.replace({name: 'search', query: {srch: srch}}`. Actually, I don't want any logic to run, I want just update the url. But the logic runs, I can't disable it (I tried to change the this.$router.listener.ready, replace the listener with some dummy function etc). It destroys the current search component, creates a new one, the input loses the focus. This all works buggy and looks buggy as well. \r\n\r\nI'm not sure if it's the nuxt's bug or the vue-router's itself. The last is strange, it misses obvious parameters like any other library has, for example one using backbone router could easily pass additional {trigger: true/false} parameter to the navigate function, but the vue-router does not have any. It has a lot of guards, but they are useless if you want to change the url, but don't want to trigger any logic behind.\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/c1468\">#c1468\u003C/a>)\u003C/em>\u003C/sub>\u003C/div>",[2975],{"name":2976,"color":2977},"2.x","d4c5f9",1642,"Update the url causes reinitialization of the current component","2023-01-18T15:42:07Z","https://github.com/nuxt/nuxt/issues/1642",0.7648518,["Reactive",2984],{},["Set"],["ShallowReactive",2987],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fIZlCxMYBUYFckusi1yafZKNxMOV-imUSg88Qwv8d7Wg":-1},"/nuxt/ui/4106"]