\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```",[3019,3022],{"name":3020,"color":3021},"enhancement","a2eeef",{"name":3023,"color":3024},"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":3034,"labels":3035,"number":3043,"owner":3026,"repository":3027,"state":3028,"title":3044,"updated_at":3045,"url":3046,"score":3047},"### 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)",[3036,3039,3040],{"name":3037,"color":3038},"bug","d73a4a",{"name":3023,"color":3024},{"name":3041,"color":3042},"triage","ffffff",4582,"SelectMenu with fetched items (ignore-filter) doesnt remember current selection","2025-07-23T17:27:36Z","https://github.com/nuxt/ui/issues/4582",0.69637376,{"description":3049,"labels":3050,"number":3054,"owner":3026,"repository":3027,"state":3028,"title":3055,"updated_at":3056,"url":3057,"score":3058},"### 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```",[3051,3052,3053],{"name":3037,"color":3038},{"name":3023,"color":3024},{"name":3041,"color":3042},4182,"Custom type with InputMenu","2025-05-19T12:22:28Z","https://github.com/nuxt/ui/issues/4182",0.70130056,{"description":3060,"labels":3061,"number":3065,"owner":3026,"repository":3027,"state":3028,"title":3066,"updated_at":3067,"url":3068,"score":3069},"### Environment\n\n- Operating System: `Windows_NT`\n- Node Version: `v22.14.0`\n- Nuxt Version: `3.17.5`\n- CLI Version: `3.25.1`\n- Nitro Version: `2.11.12`\n- Package Manager: `npm@10.9.2`\n- Builder: `-`\n- User Config: `compatibilityDate`, `devtools`, `modules`, `css`, `colorMode`, `build`, `runtimeConfig`, `app`, `lodash`, `pages`, `components`, `vite`, `router`, `nitro`\n- Runtime Modules: `@pinia/nuxt@0.11.1`, `pinia-plugin-persistedstate/nuxt@4.3.0`, `@vueuse/nuxt@13.3.0`, `nuxt-countdown@1.2.0`, `nuxt-lodash@2.5.3`, `@nuxt/eslint@1.4.1`, `@nuxt/fonts@0.11.4`, `@nuxt/icon@1.13.0`, `@nuxt/ui@3.1.3`\n- Build Modules: `-`\n\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.17.5\n\n### Reproduction\n\nhttps://codesandbox.io/p/devbox/hopeful-wilbur-xmxvdn\n\n### Description\n\nUSelect does not recognize undefined as a valid option, and does not highlight that option as selected.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3062,3063,3064],{"name":3037,"color":3038},{"name":3023,"color":3024},{"name":3041,"color":3042},4373,"USelect doesn't accept undefined as selected option","2025-06-18T12:37:16Z","https://github.com/nuxt/ui/issues/4373",0.7023607,{"description":3071,"labels":3072,"number":3077,"owner":3026,"repository":3027,"state":3028,"title":3078,"updated_at":3079,"url":3080,"score":3081},"### Description\n\nI have a file field **without** `v-model`, then I select a file. I have another field with a validation error. On submit, the validation error is shown on the email field and the file field is cleared. Is this a bug or a feature. With version `3.2.0` this behaviour does not exist. In `3.3.0` it does. It might be related to one of the dependencies though, because if I first upgrade to 3.3.0 and then go back to 3.2.0, where the lockfile still shows a lot of changes, the problem still exists.\n\n```vue\n\u003Cscript setup lang=\"ts\">\nimport type { FormError, FormSubmitEvent } from '#ui/types'\n\nconst state = reactive({\n email: undefined,\n file: undefined,\n})\n\nconst validate = (): FormError[] => {\n const errors = []\n errors.push({ name: 'email', message: 'Required' })\n return errors\n}\n\nasync function onSubmit(event: FormSubmitEvent\u003Ctypeof state>) {\n console.log(event.data)\n}\n\u003C/script>\n\n\u003Ctemplate>\n \u003CUForm\n :validate=\"validate\"\n :state=\"state\"\n class=\"space-y-4\"\n @submit=\"onSubmit\"\n\n \u003CUFormField label=\"Email\" name=\"email\">\n \u003CUInput v-model=\"state.email\" />\n \u003C/UFormField>\n\n \u003CUFormField label=\"File\" name=\"file\">\n \u003CUInput type=\"file\" />\n \u003C/UFormField>\n\n \u003CUButton type=\"submit\"> Submit \u003C/UButton>\n \u003C/UForm>\n\u003C/template>\n```",[3073,3076],{"name":3074,"color":3075},"question","d876e3",{"name":3023,"color":3024},4637,"File field gets cleared, bug?","2025-07-31T09:13:25Z","https://github.com/nuxt/ui/issues/4637",0.70336056,{"description":3083,"labels":3084,"number":3088,"owner":3026,"repository":3027,"state":3089,"title":3090,"updated_at":3091,"url":3092,"score":3093},"### 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```",[3085,3086,3087],{"name":3037,"color":3038},{"name":3023,"color":3024},{"name":3041,"color":3042},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":3095,"labels":3096,"number":3100,"owner":3026,"repository":3027,"state":3089,"title":3101,"updated_at":3102,"url":3103,"score":3104},"### 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```",[3097,3098,3099],{"name":3037,"color":3038},{"name":3023,"color":3024},{"name":3041,"color":3042},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":3106,"labels":3107,"number":3117,"owner":3026,"repository":3027,"state":3089,"title":3118,"updated_at":3119,"url":3120,"score":3121},"### 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```",[3108,3109,3112,3113,3114],{"name":3037,"color":3038},{"name":3110,"color":3111},"needs reproduction","CB47CF",{"name":3023,"color":3024},{"name":3041,"color":3042},{"name":3115,"color":3116},"closed-by-bot","ededed",4103,"InputMenu Event onChange","2025-05-17T02:08:14Z","https://github.com/nuxt/ui/issues/4103",0.66421723,{"description":3123,"labels":3124,"number":3130,"owner":3026,"repository":3027,"state":3089,"title":3131,"updated_at":3132,"url":3133,"score":3134},"### 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```",[3125,3126,3127,3128],{"name":3037,"color":3038},{"name":3023,"color":3024},{"name":3041,"color":3042},{"name":3129,"color":3116},"stale",3194,"[Select] Buggy behaviour of Select fields when used with vee-validate","2025-06-12T15:32:10Z","https://github.com/nuxt/ui/issues/3194",0.67459184,{"description":3136,"labels":3137,"number":3141,"owner":3026,"repository":3026,"state":3089,"title":3142,"updated_at":3143,"url":3144,"score":3145},"### 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_",[3138],{"name":3139,"color":3140},"pending triage","E99695",28733,"SelectMenu initial object values","2024-08-28T03:27:34Z","https://github.com/nuxt/nuxt/issues/28733",0.67879945,["Reactive",3147],{},["Set"],["ShallowReactive",3150],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fqKbVY_Yx5d-Z9gw1dI4DRNmMoNws3RIesFzRqhI_97U":-1},"/nuxt/ui/3736"]