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_",[3204,3207,3209],{"name":3205,"color":3206},"duplicate","cfd3d7",{"name":3140,"color":3208},"a2eeef",{"name":3165,"color":3166},4172,"closed","Uselect and UselectMenu content infinite scroll","2025-05-23T13:55:50Z","https://github.com/nuxt/ui/issues/4172",0.6958113,{"description":3217,"labels":3218,"number":3226,"owner":3152,"repository":3168,"state":3211,"title":3227,"updated_at":3228,"url":3229,"score":3230},"### For what version of Nuxt UI are you suggesting this?\n\nv2.x\n\n### Description\n\nHi I would like to have within the component UselectMenu emit the event \"scroll\" \nwith the following properties: \n```\n{\n target: HTMLElement, \n currentTarget: HTMLElement, \n scrollTop: number,\n scrollHeight: number, \n clientHeight: number, \n}\n```\n\n to dynamically remote search items through an api and append it dynamically to my USelectMenu to create an infinite scroll. \n\nThis feature would be great in both version :)\n\n### Additional context\n\n_No response_",[3219,3220,3221,3224],{"name":3140,"color":3208},{"name":3181,"color":3182},{"name":3222,"color":3223},"closed-by-bot","ededed",{"name":3225,"color":3223},"stale",2793,"add an emit \"scroll\" event for USelectMenu","2025-06-18T09:05:29Z","https://github.com/nuxt/ui/issues/2793",0.7111876,{"description":3232,"labels":3233,"number":3237,"owner":3152,"repository":3168,"state":3211,"title":3238,"updated_at":3239,"url":3240,"score":3241},"### 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)",[3234,3235,3236],{"name":3177,"color":3178},{"name":3165,"color":3166},{"name":3181,"color":3182},4582,"SelectMenu with fetched items (ignore-filter) doesnt remember current selection","2025-08-14T09:04:53Z","https://github.com/nuxt/ui/issues/4582",0.7133913,{"description":3243,"labels":3244,"number":3247,"owner":3152,"repository":3168,"state":3211,"title":3248,"updated_at":3249,"url":3250,"score":3251},"### 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_",[3245,3246],{"name":3140,"color":3208},{"name":3181,"color":3182},2882,"USelectMenu: Manually trigger the search query","2025-05-10T17:19:44Z","https://github.com/nuxt/ui/issues/2882",0.73104566,{"description":3253,"labels":3254,"number":3259,"owner":3152,"repository":3168,"state":3211,"title":3260,"updated_at":3261,"url":3262,"score":3263},"### Description\n\nI want to use the `InputMenu` component with multiple selections and a list of data retrieved from an API.\nHowever, when I select an item through a search, it is not displayed correctly because its data is not necessarily present in the list of available options returned by the API.\n\nA reproduction of my situation is available on this [CodeSandbox](https://codesandbox.io/p/devbox/upbeat-snyder-m27rfr) in the `index.vue` page.\nFor an example, search for the first name “Emma” and select the two suggested items. The first one is found in the initial range of data available from the API, while the other is located in a more distant range.\n\nDo you have any ideas on possible solutions to resolve this issue? Could it perhaps be a bug in the component?",[3255,3256,3257,3258],{"name":3162,"color":3163},{"name":3165,"color":3166},{"name":3222,"color":3223},{"name":3225,"color":3223},3348,"InputMenu multiple with async data","2025-06-18T09:02:06Z","https://github.com/nuxt/ui/issues/3348",0.7390187,{"description":3265,"labels":3266,"number":3267,"owner":3152,"repository":3152,"state":3211,"title":3268,"updated_at":3269,"url":3270,"score":3271},"I had an issue with my query's on the [...uri].vue in Nuxt 3, where the pages between the uri already loaded and after that they transitioned.\r\n\r\nChanging the query from `useFetch` to `useLazyFetch`\r\nThink this would also work for `useAsyncData` to `useLazyAsyncData`\r\n\r\nI think the thing about it is that Fetch immediately takes the query up to the next frame, and with Lazy you have a well lazy moment.\r\n\r\nHope this fixes for everyone who encounters it.\r\n\r\nDon't think it really is a bug/issue, rather then just a query which is very quick ;)\r\n\r\n_Originally posted by @TinyLightBold in https://github.com/nuxt/nuxt/issues/4132#issuecomment-1551655487_\r\n ",[],20920,"Possible fix for Page Transition between [..uri].vue","2023-06-29T05:20:52Z","https://github.com/nuxt/nuxt/issues/20920",0.7424648,["Reactive",3273],{},["Set"],["ShallowReactive",3276],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$f8OWeUD6Ox2GpkPI6YFm8UXqgT_GKL6sXl-mFssbkxPw":-1},"/nuxt/ui/2744"]