\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.63475555,{"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: Linux\n- Node Version: v20.9.0\n- Nuxt Version: 3.15.3\n- CLI Version: 3.20.0\n- Nitro Version: 2.10.4\n- Package Manager: pnpm@9.13.1\n- Builder: -\n- User Config: compatibilityDate, devtools, modules, css\n- Runtime Modules: @nuxt/ui@3.0.0-alpha.12, @vee-validate/nuxt@4.15.0\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.0.0-alpha.12\n\n### Reproduction\n\nhttps://stackblitz.com/~/github.com/arpadgabor/nuxt-ui-3-bug\n\nIn case the above link does not work, here is the repo: https://github.com/arpadgabor/nuxt-ui-3-bug\n\n### Description\n\nWhen using the Select and SelectMenu components with vee-validate, especially when there are multiple fields involved, there is a very weird behaviour. Selection does not work correctly, cannot close the dropdown, etc. I've added a recording as well (I keep clicking outside and on the menu options).\n\nhttps://github.com/user-attachments/assets/bc8aa97c-377c-4f57-ab7d-55929f30d97c\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2873,2876,2877],{"name":2874,"color":2875},"bug","d73a4a",{"name":2860,"color":2861},{"name":2878,"color":2879},"triage","ffffff",3194,"[Select] Buggy behaviour of Select fields when used with vee-validate","2025-01-28T18:58:50Z","https://github.com/nuxt/ui/issues/3194",0.67172617,{"description":2886,"labels":2887,"number":2891,"owner":2863,"repository":2864,"state":2865,"title":2892,"updated_at":2893,"url":2894,"score":2895},"### Environment\n\n- Operating System: Darwin\n- Node Version: v23.11.0\n- Nuxt Version: 3.17.3\n- CLI Version: 3.25.1\n- Nitro Version: 2.11.12\n- Package Manager: npm@10.9.2\n- Builder: -\n- User Config: devtools, typescript, css, compatibilityDate, devServer, vite, runtimeConfig, app, ui, scripts, modules, sentry, sourcemap\n- Runtime Modules: @nuxt/ui@3.1.2, @pinia/nuxt@0.11.0, pinia-plugin-persistedstate/nuxt@4.3.0, @sentry/nuxt/module@9.19.0, @nuxt/scripts@0.11.7, @nuxt/eslint@1.4.0\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.1.2\n\n### Reproduction\n\nhttps://codesandbox.io/p/devbox/r7ryl3\n\n### Description\n\nI recently upgrade to NuxtUI 3.1.2 (from 3.0.1) and It's impossible (or I don't know) how to deal with custom type for `InputMenu`, I got some types issues on `label-key`, `v-model`, `items`, `slots` as you can see in my reproduction.\n\n### Additional context\n\n\n\n### Logs\n\n```shell-script\n\n```",[2888,2889,2890],{"name":2874,"color":2875},{"name":2860,"color":2861},{"name":2878,"color":2879},4182,"Custom type with InputMenu","2025-05-19T12:22:28Z","https://github.com/nuxt/ui/issues/4182",0.70130056,{"description":2897,"labels":2898,"number":2902,"owner":2863,"repository":2864,"state":2865,"title":2903,"updated_at":2904,"url":2905,"score":2906},"### Environment\n\n- Operating System: Windows_NT\n- Node Version: v22.14.0\n- Nuxt Version: 3.17.1\n- CLI Version: 3.25.0\n- Nitro Version: 2.11.11\n- Package Manager: npm@10.9.2\n- Builder: -\n- User Config: compatibilityDate, future, devtools, app, runtimeConfig, hooks, components, modules, eslint, ui, css, telemetry\n- Runtime Modules: @nuxt/eslint@1.3.0, @nuxt/ui@3.1.1, @pinia/nuxt@0.11.0\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.1.1\n\n### Reproduction\n\n1. Add a `USelect` component to a page with any example from the official doc: https://ui.nuxt.com/components/select\n2. Start dev mode: `npm run dev`\n3. Opens the page and try interact with the select element with **Vue dev tool opened**\n\n### Description\n\nThe `USelect` component responds really slow upon user clicks (20+ seconds to open/close for a select with 100+ items), this also applies to some other components such as `UDropdownMenu` and `USelectMenu`.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2899,2900,2901],{"name":2874,"color":2875},{"name":2860,"color":2861},{"name":2878,"color":2879},4142,"USelect and USelectMenu responds really slow when Vue devtool is opened","2025-05-13T13:28:11Z","https://github.com/nuxt/ui/issues/4142",0.70660186,{"description":2908,"labels":2909,"number":2913,"owner":2863,"repository":2864,"state":2865,"title":2914,"updated_at":2915,"url":2916,"score":2917},"### Environment\n\nOperating System: Windows 11\nNode Version: v22.14.0\nNuxt Version: 3.17.4\nNitro Version: 2.11.12\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.1.3\n\n### Description\n\nHi,\nWhen I use the mouseenter and mouseleave or mouseover and mouseout events, the following error appears and the events don't work:\n\n\"[Vue warn]: Extraneous non-emits event listeners (mouseenter, mouseleave) were passed to component but could not be automatically inherited because component renders fragment or text root nodes. If the listener is intended to be a component custom event listener only, declare it using the emits option.\"\n\nWhat should I do? Can you help me?\n",[2910,2911,2912],{"name":2874,"color":2875},{"name":2860,"color":2861},{"name":2878,"color":2879},4268,"Extraneous non-emits event listeners (mouseenter, mouseleave) on UDashboardSidebar component","2025-06-01T11:15:46Z","https://github.com/nuxt/ui/issues/4268",0.7112175,{"description":2919,"labels":2920,"number":2924,"owner":2863,"repository":2864,"state":2925,"title":2926,"updated_at":2927,"url":2928,"score":2929},"### Environment\n\n------------------------------\n- Operating System: Darwin\n- Node Version: v22.13.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.4\n- Builder: -\n- User Config: compatibilityDate, devtools, runtimeConfig, nitro, routeRules, modules, ui, supabase, site, feed, sitemap, robots, schemaOrg, image, hub\n- Runtime Modules: @nuxt/ui@3.0.1, @nuxtjs/supabase@1.5.0, @vueuse/nuxt@13.0.0, @nuxt/image@1.10.0, @nuxthub/core@0.8.18, @nuxtjs/sitemap@7.2.9, nuxt-module-feed@1.1.4, @nuxtjs/robots@5.2.8, nuxt-schema-org@5.0.4, nuxt-link-checker@4.3.0\n- Build Modules: -\n------------------------------\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.0.1\n\n### Reproduction\n\nhttps://codesandbox.io/p/devbox/adoring-gates-fd8q9s\n\n### Description\n\n## Expected behaviour\nValidation should trigger when a user adds or removes items from an input menu that has the `multiple` prop\n\n## Actual behaviour\nValidation seems to trigger when the input menu is opened or closed, but not when items are removed\n\n## Reproduction\n1. Use the codesandbox provided\n2. Add all 4 items to the input\n3. Validation should trigger saying 3 max\n4. Remove an item\n5. **Validation error persists, when it should be gone**\n6. Remove all the items\n7. Add a single item\n8. Remove them item\n9. **Validation error should appear stating 1 item min, but it doesn't**\n\n### Additional context\n\n## Screen capture\n\nhttps://github.com/user-attachments/assets/fccda9b1-2837-4b7d-85ad-5d63480582a1\n\n### Logs\n\n```shell-script\n\n```",[2921,2922,2923],{"name":2874,"color":2875},{"name":2860,"color":2861},{"name":2878,"color":2879},3726,"closed","Form validation with InputMenu doesn't trigger when expected","2025-04-08T19:48:00Z","https://github.com/nuxt/ui/issues/3726",0.6424647,{"description":2931,"labels":2932,"number":2936,"owner":2863,"repository":2864,"state":2925,"title":2937,"updated_at":2938,"url":2939,"score":2940},"### Environment\n\n- Operating System: `Darwin`\n- Node Version: `v22.13.0`\n- Nuxt Version: `3.16.2`\n- CLI Version: `3.24.1`\n- Nitro Version: `2.11.9`\n- Package Manager: `pnpm@10.8.1`\n- Builder: `-`\n- User Config: `modules`, `devtools`, `css`, `site`, `future`, `compatibilityDate`, `echarts`, `eslint`, `fonts`, `icon`, `sitemap`\n- Runtime Modules: `@nuxtjs/sitemap@7.2.10`, `@nuxt/content@3.4.0`, `@nuxt/eslint@1.3.0`, `@nuxt/ui-pro@3.0.2`, `@vueuse/nuxt@13.1.0`, `nuxt-echarts@0.3.0`\n- Build Modules: `-`\n\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.0.2\n\n### Reproduction\n\nhttps://codesandbox.io/p/devbox/peaceful-elbakyan-3ddsxd\n\n### Description\n\nMy understanding is that the onSelect event of SelectMenu should be consistent with the DropdownMenu component, but in reality, it is not.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2933,2934,2935],{"name":2874,"color":2875},{"name":2860,"color":2861},{"name":2878,"color":2879},3978,"The onSelect event of the SelectMenu component was not triggered","2025-05-05T15:20:55Z","https://github.com/nuxt/ui/issues/3978",0.6495051,{"description":2942,"labels":2943,"number":2953,"owner":2863,"repository":2864,"state":2925,"title":2954,"updated_at":2955,"url":2956,"score":2957},"### Environment\n\nNuxt project info: (copied to clipboard) nuxi 10:36:44\n\n------------------------------\n- Operating System: Windows_NT\n- Node Version: v20.9.0\n- Nuxt Version: 3.16.0\n- CLI Version: 3.25.0\n- Nitro Version: 2.11.11\n- Package Manager: npm@10.9.0\n- Builder: -\n- User Config: devtools, modules, css, future, compatibilityDate, experimental, nitro, sourcemap, ssr, spaLoadingTemplate, runtimeConfig\n- Runtime Modules: @nuxt/ui@3.1.1, @nuxtjs/mdc@0.15.0, @vueuse/nuxt@13.1.0\n- Build Modules: -\n------------------------------\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.1.1\n\n### Reproduction\n\n\nInput Menu Send an event when using @Change\n\n\n\nBut it is scheduled to send a value and this generates the error in console\n\n\n\n\n\n### Description\n\nhttps://github.com/user-attachments/assets/3fdd5798-3f77-45e0-a86b-18a2195219f2\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2944,2945,2948,2949,2950],{"name":2874,"color":2875},{"name":2946,"color":2947},"needs reproduction","CB47CF",{"name":2860,"color":2861},{"name":2878,"color":2879},{"name":2951,"color":2952},"closed-by-bot","ededed",4103,"InputMenu Event onChange","2025-05-17T02:08:14Z","https://github.com/nuxt/ui/issues/4103",0.66421723,{"description":2959,"labels":2960,"number":2964,"owner":2863,"repository":2863,"state":2925,"title":2965,"updated_at":2966,"url":2967,"score":2968},"### 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_",[2961],{"name":2962,"color":2963},"pending triage","E99695",28733,"SelectMenu initial object values","2024-08-28T03:27:34Z","https://github.com/nuxt/nuxt/issues/28733",0.67879945,{"description":2970,"labels":2971,"number":2975,"owner":2863,"repository":2864,"state":2925,"title":2976,"updated_at":2977,"url":2978,"score":2979},"### Environment\n\n- Operating System: `Darwin`\n- Node Version: `v22.13.0`\n- Nuxt Version: `3.16.2`\n- CLI Version: `3.24.0`\n- Nitro Version: `2.11.8`\n- Package Manager: `pnpm@10.9.0`\n- Builder: `-`\n- User Config: `-`\n- Runtime Modules: `-`\n- Build Modules: `-`\n\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nnuxt-ui 3.1.0\n\n### Reproduction\n\nhttps://ui.nuxt.com/components/form\n\nOpen in Chrome and check `issues` in devtools. The linked erroring nodes are all RadioGroups or CheckboxGroups.\n\n### Description\n\nThe FormField component correctly removes the `for` attribute from the label for the RadioGroup & CheckboxGroup components. Chrome devtools would suggest that there should be a further step so that `\u003Clabel>` is not used at all in this context.\n\nI am happy to propose changes.\n\n\u003Cimg width=\"917\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/2f3f5fc1-d819-4974-9217-6ab75f31cf64\" />\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2972,2973,2974],{"name":2874,"color":2875},{"name":2860,"color":2861},{"name":2878,"color":2879},3998,"Chrome reports the FormField label as `Incorrect use of \u003Clabel for=FORM_ELEMENT>` when wrapping RadioGroup or CheckboxGroup","2025-05-15T09:32:18Z","https://github.com/nuxt/ui/issues/3998",0.6930073,["Reactive",2981],{},["Set"],["ShallowReactive",2984],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fqKbVY_Yx5d-Z9gw1dI4DRNmMoNws3RIesFzRqhI_97U":-1},"/nuxt/ui/3736"]