and \u003CUSelectMenu /> components render options within a fixed-height dropdown. It is complicated to deal with large datasets. When displaying large lists of options, this can lead to performance issues. Is it possible we can get something like VueUse infinite scroll?\n[https://vueuse.org/core/useinfinitescroll/#useinfinitescroll](url) ??\n\n### Additional context\n\n_No response_",[2905,2908,2910],{"name":2906,"color":2907},"duplicate","cfd3d7",{"name":2857,"color":2909},"a2eeef",{"name":2879,"color":2880},4172,"closed","Uselect and UselectMenu content infinite scroll","2025-05-23T13:55:50Z","https://github.com/nuxt/ui/issues/4172",0.7322785,{"description":2918,"labels":2919,"number":2928,"owner":2866,"repository":2885,"state":2912,"title":2929,"updated_at":2930,"url":2931,"score":2932},"### 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```",[2920,2921,2924,2925],{"name":2876,"color":2877},{"name":2922,"color":2923},"needs reproduction","CB47CF",{"name":2879,"color":2880},{"name":2926,"color":2927},"closed-by-bot","ededed",4098,"Unable to use search input inside UDropdownMenu","2025-06-03T02:11:42Z","https://github.com/nuxt/ui/issues/4098",0.73485076,{"description":2934,"labels":2935,"number":2938,"owner":2866,"repository":2885,"state":2912,"title":2939,"updated_at":2940,"url":2941,"score":2942},"### Environment\n\n- Operating System: Darwin\n- Node Version: v23.4.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.5\n- Builder: -\n- User Config: devtools, modules, imports, components, css, compatibilityDate, experimental, future\n- Runtime Modules: @nuxt/ui@3.0.0\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.0.0\n\n### Reproduction\n\nhttps://codesandbox.io/p/devbox/recursing-browser-klwx46\n\n### Description\n\nWhen a `SelectMenu` is wrapped in a custom component which is then consumed by `FormField` validation is triggered for an instant before the component goes back to its valid state.\n\nI've tried to debug a bit and I think it's related to the fact that the `SelectMenu` uses `Input` and that input is firing a `change` event because it uses `useFormField`, even though that particular input should not be considered the \"form field\" in this instance.\n\n### Additional context\n\nhttps://github.com/user-attachments/assets/75e8c84f-612e-48f0-bf9e-dcc1fe95ffcd\n\nI'd like to open a PR and fix this myself but I'm not sure what the best approach it. Maybe `Input` could take a prop that allows it to not fire form events? i.e. `ignore-form-events=\"true\"` so the SelectMenu would use it. This could also apply for other components that use primitive form inputs inside them (Command, InputMenu) etc.\n\n### Logs\n\n```shell-script\n\n```",[2936,2937],{"name":2876,"color":2877},{"name":2879,"color":2880},3736,"[USelectMenu] Validation events are triggered before change when wrapped in a custom component","2025-05-14T17:24:48Z","https://github.com/nuxt/ui/issues/3736",0.73907727,{"description":2944,"labels":2945,"number":2949,"owner":2866,"repository":2866,"state":2912,"title":2950,"updated_at":2951,"url":2952,"score":2953},"### 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_",[2946],{"name":2947,"color":2948},"pending triage","E99695",28733,"SelectMenu initial object values","2024-08-28T03:27:34Z","https://github.com/nuxt/nuxt/issues/28733",0.74211574,{"description":2955,"labels":2956,"number":2961,"owner":2866,"repository":2866,"state":2912,"title":2962,"updated_at":2963,"url":2964,"score":2965},"### Environment\n\n- Operating System: `Darwin`\r\n- Node Version: `v19.5.0`\r\n- Nuxt Version: `3.2.3`\r\n- Nitro Version: `2.2.3`\r\n- Package Manager: `npm@9.3.1`\r\n- Builder: `vite`\r\n- User Config: `modules`, `runtimeConfig`, `content`, `image`, `googleFonts`\r\n- Runtime Modules: `@nuxt/content@2.5.2`, `@nuxtjs/google-fonts@3.0.0`, `@nuxt/image-edge@1.0.0-27968280.9739e4d`\r\n- Build Modules: `-`\r\n\n\n### Reproduction\n\nThe following code fetches search results. It's automatically refreshed when the searchquery ref is changed.\r\n\r\n```javascript\r\nconst navSearchAPICall = useLazyAsyncData(\r\n 'searchWorking',\r\n () => $fetch('/api/search', {\r\n params: {\r\n query: searchquery.value\r\n }\r\n }),\r\n { \r\n server: false,\r\n watch: [searchquery]\r\n }\r\n)\r\n```\r\n\r\nThis works as expected. But the following code, wich should behave the same according to the documentation, does not work. The request is refreshed when the searchquery ref changes, but the query parameters stay the same.\r\n\r\n```javascript\r\nconst searchAPICall = useLazyFetch('/api/search', {\r\n key: 'searchNotWorking',\r\n params: {\r\n query: searchquery.value\r\n },\r\n server: false,\r\n watch: [searchquery]\r\n }\r\n)\r\n```\r\n\r\n\r\n\n\n### Describe the bug\n\nAs described in the reproduction, when using `useLazyAsyncData`, the request is refreshed with updated query parameters according to the searchquery ref. \r\n\r\nBut when using `useLazyFetch`, the request is refreshed but sent with unchanged query parameters.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2957,2960],{"name":2958,"color":2959},"3.x","29bc7f",{"name":2947,"color":2948},19665,"useLazyFetch does not behave like useLazyAsyncData","2023-03-14T11:09:45Z","https://github.com/nuxt/nuxt/issues/19665",0.7426828,{"description":2967,"labels":2968,"number":2972,"owner":2866,"repository":2866,"state":2912,"title":2973,"updated_at":2974,"url":2975,"score":2976},"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>",[2969],{"name":2970,"color":2971},"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.7434408,{"description":2978,"labels":2979,"number":2985,"owner":2866,"repository":2885,"state":2912,"title":2986,"updated_at":2987,"url":2988,"score":2989},"### Description\n\nCurrently, I want to use the InputMenu for URL suggestions. The user can choose whether they want to select one of the suggestions or enter their own URL. There are several InputMenus, which means that the user usually wants to jump to the next field using the tab key. \n\nHowever, this is not so easy with the InputMenu. With `create-items`, the field expects a click or enter to be entered. There is no autocreate. \n\nI have also tried using `update:search-terms`, which worked well as long as the user treated it as a pure input field. However, in this case, no suggestions appear. And if the user selects a suggestion, the VModel is also empty – more precisely, it gets a value and is deleted shortly afterwards.\n\nTherefore, it would be desirable if create-items could be set to transfer the input to the V-Model immediately, or if there was a general mode in which the input field treats the suggestions as optional.\n\n\n\n### Additional context\n\n_No response_",[2980,2981,2982,2983,2984],{"name":2857,"color":2909},{"name":2922,"color":2923},{"name":2879,"color":2880},{"name":2882,"color":2883},{"name":2926,"color":2927},4106,"InputMenu with Autocreate","2025-05-18T02:13:24Z","https://github.com/nuxt/ui/issues/4106",0.74866027,["Reactive",2991],{},["Set"],["ShallowReactive",2994],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fyxhV-p5GamP4OozeiPg4mJTYBxJKqu8bIV-SLfULOCI":-1},"/nuxt/ui/2882"]