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_",[2969,2972,2973],{"name":2970,"color":2971},"duplicate","cfd3d7",{"name":2904,"color":2953},{"name":2926,"color":2927},4172,"Uselect and UselectMenu content infinite scroll","2025-05-23T13:55:50Z","https://github.com/nuxt/ui/issues/4172",0.7322785,{"description":2980,"labels":2981,"number":2988,"owner":2913,"repository":2932,"state":2961,"title":2989,"updated_at":2990,"url":2991,"score":2992},"### 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```",[2982,2983,2986,2987],{"name":2923,"color":2924},{"name":2984,"color":2985},"needs reproduction","CB47CF",{"name":2926,"color":2927},{"name":2956,"color":2957},4098,"Unable to use search input inside UDropdownMenu","2025-06-03T02:11:42Z","https://github.com/nuxt/ui/issues/4098",0.73485076,{"description":2994,"labels":2995,"number":3000,"owner":2913,"repository":2932,"state":2961,"title":3001,"updated_at":3002,"url":3003,"score":3004},"### Environment\n\n- Operating System: Linux\n- Node Version: v18.20.3\n- Nuxt Version: 3.14.1592\n- CLI Version: 3.15.0\n- Nitro Version: 2.10.4\n- Package Manager: pnpm@8.15.6\n- Builder: -\n- User Config: default\n- Runtime Modules: @nuxt/ui@2.19.2\n- Build Modules: -\n\n### Version\n\n2.19.2(vite@5.4.11)(vue@3.5.13)\n\n### Reproduction\n\nhttps://stackblitz.com/edit/nuxt-ui-dvarzb\n\n### Description\n\nI tried to add new functionality on USelectMenu to have information icon on select menu option so that when you hover on it, it will trigger UPopover to display important detail of the object including an action button to open a slideover. \n\nI tried it on multiple mode and single mode. But the implementation was not working on single mode. To give you more context, I'm using `@mouseenter` and `@mouseleave` events on the popover panel slot in order to detect whether I'm on the popover panel and to prevent clicking the option when I'm clicking the `Open detailed view` button.\n\n\n\nThe issue was when I'm in single mode and tried to hover on the icon then clicked the `Open detailed view` button, it closes both the popover and the select menu.\n\nI expect it would open the slide over both in multiple and single select menu.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2996,2997,2998,2999],{"name":2923,"color":2924},{"name":2929,"color":2930},{"name":2956,"color":2957},{"name":2959,"color":2957},2753,"[USelectMenu] [UPopover] Can't open click button inside popover panel in select menu option","2025-06-18T09:05:35Z","https://github.com/nuxt/ui/issues/2753",0.73824644,{"description":3006,"labels":3007,"number":3010,"owner":2913,"repository":2932,"state":2961,"title":3011,"updated_at":3012,"url":3013,"score":3014},"### 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```",[3008,3009],{"name":2923,"color":2924},{"name":2926,"color":2927},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":3016,"labels":3017,"number":3021,"owner":2913,"repository":2913,"state":2961,"title":3022,"updated_at":3023,"url":3024,"score":3025},"### 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_",[3018],{"name":3019,"color":3020},"pending triage","E99695",28733,"SelectMenu initial object values","2024-08-28T03:27:34Z","https://github.com/nuxt/nuxt/issues/28733",0.74211574,{"description":3027,"labels":3028,"number":3033,"owner":2913,"repository":2913,"state":2961,"title":3034,"updated_at":3035,"url":3036,"score":3037},"### 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_",[3029,3032],{"name":3030,"color":3031},"3.x","29bc7f",{"name":3019,"color":3020},19665,"useLazyFetch does not behave like useLazyAsyncData","2023-03-14T11:09:45Z","https://github.com/nuxt/nuxt/issues/19665",0.7426828,["Reactive",3039],{},["Set"],["ShallowReactive",3042],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fyxhV-p5GamP4OozeiPg4mJTYBxJKqu8bIV-SLfULOCI":-1},"/nuxt/ui/2882"]