\n\n### Description\n\nThe UInputTag element does not correctly render the error text for schema validation errors for pattern matching of the individual items within its array. \n\nIt works fine showing an error about the length of the array, but not about problems for the items within the array.\n\n\u003Cimg width=\"779\" height=\"328\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/cf031108-314b-4fd5-9859-cd275b8d3410\" />\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3050,3051,3052],{"name":3020,"color":3021},{"name":3023,"color":3024},{"name":3026,"color":3027},4573,"UInputTag does not display validation errors for pattern matching","2025-07-22T14:39:33Z","https://github.com/nuxt/ui/issues/4573",0.70000523,{"description":3059,"labels":3060,"number":3064,"owner":3029,"repository":3030,"state":3065,"title":3066,"updated_at":3067,"url":3068,"score":3069},"### Environment\n\n- Operating System: Windows_NT\n- Node Version: v24.2.0\n- Nuxt Version: 3.17.7\n- CLI Version: 3.25.1\n- Nitro Version: 2.11.13\n- Package Manager: bun@1.2.17\n- Builder: -\n- User Config: future, experimental, css, modules, nitro, i18n, imports, runtimeConfig, icon, compatibilityDate\n- Runtime Modules: @nuxtjs/i18n@9.5.6, @nuxt/ui-pro@3.2.0, @nuxt/eslint@1.5.2, @nuxtjs/html-validator@2.1.0, @nuxt/image@1.10.0, @vueuse/nuxt@13.5.0, @artmizu/nuxt-prometheus@2.5.0, @nuxtjs/seo@3.1.0\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.2.0\n\n### Reproduction\n\nThe issue is really straight-forward, example code: \n\n```vue\n\u003Cscript lang=\"ts\" setup>\nconst value = ref(\"\");\nconst items = [\"Item 1\", \"Item 2\", \"Item 3\"];\n\u003C/script>\n\n\u003Ctemplate>\n \u003Cdiv class=\"space-y-4\">\n \u003CUFormField label=\"USelectMenu\">\n \u003CUSelectMenu v-model=\"value\" placeholder=\"Placeholder\" :items />\n \u003C/UFormField>\n \u003CUFormField label=\"USelect\">\n \u003CUSelect v-model=\"value\" placeholder=\"Placeholder\" :items />\n \u003C/UFormField>\n \u003C/div>\n\u003C/template>\n\n```\n\n### Description\n\nIf the model-value is an empty string, the USelectMenu placeholder doesn't show. This behavior is different than the USelect component, where the placeholder is shown without having to use `undefined` as the v-model's value. \n\n### Additional context\n\nI know I could use `undefined` for the value here, however in my real code the v-model is bound to a non-optional value, so if I were to initialize it as `undefined`, TypeScript would freak out. Also, because these components are really similar, these behaviors shouldn't differ in my opinion. \n\n\u003Cimg width=\"200\" height=\"143\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/49a5d11d-2212-41d7-81b3-202692a20a8a\" />\n\n### Logs\n\n```shell-script\n\n```",[3061,3062,3063],{"name":3020,"color":3021},{"name":3023,"color":3024},{"name":3026,"color":3027},4528,"closed","[SelectMenu]: Placeholder value not shown if v-model is an empty string","2025-07-16T10:43:41Z","https://github.com/nuxt/ui/issues/4528",0.6276549,{"description":3071,"labels":3072,"number":3075,"owner":3029,"repository":3030,"state":3065,"title":3076,"updated_at":3077,"url":3078,"score":3079},"### Environment\n\n- Operating System: Windows_NT\n- Node Version: v22.14.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: modules, css, build, supabase, content, pinia, devtools, debug, routeRules, future, compatibilityDate, eslint\n- Runtime Modules: @nuxt/eslint@1.3.0, @nuxt/ui-pro@3.1.0, @vueuse/nuxt@13.1.0, @nuxt/content@3.5.1, @nuxt/icon@1.12.0, @nuxt/image@1.10.0, @nuxt/scripts@0.11.6, @nuxt/test-utils@3.17.2, @nuxtjs/supabase@1.5.0, @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.0\n\n### Reproduction\n\n```\n\u003Ctemplate>\n \u003Cdiv class=\"flex\">\n \u003CUForm :state=\"state\" class=\"w-1/2 p-4\">\n \u003CUFormField v-for=\"(item, index) in items\" :key=\"index\" :label=\"index\" :name=\"index\">\n \u003CUColorPicker v-if=\"index == 'color'\" v-model=\"state[index]\" :default-value=\"item\" />\n \u003CUSlider v-if=\"index == 'range' && typeof item == 'number'\" v-model=\"state[index]\" :default-value=\"item\" />\n \u003CUInput v-if=\"typeof state[index] == 'boolean'\" :type=\"index\" :value=\"index\" :checked=\"item\" />\n \u003CUInput v-else :type=\"index\" v-model=\"state[index]\" :default-value=\"item\" />\n \u003C/UFormField>\n \u003C/UForm>\n \u003Cpre class=\"w-1/2 bg-gray-200 p-4 leading-14\"> {{ state }} \u003C/pre>\n \u003C/div>\n\u003C/template>\n\n\u003Cscript lang=\"ts\" setup>\nconst state = ref({}) // ISSUE: Default values are not loaded in the v-model\nconst items = {\n number: 50,\n reset: true, // ISSUE: UInput is not supporting boolean values for v-model\n submit: true, // ISSUE: UInput is not supporting boolean values for v-model\n search: \"search\",\n date: \"2025-04-25\",\n text: \"text\",\n color: \"#ccffcc\",\n button: true, // ISSUE: UInput is not supporting boolean values for v-model\n checkbox: false, // ISSUE: UInput is not supporting boolean values for v-model\n \"datetime-local\": \"2025-04-25T10:49:31\",\n email: \"nobody@gmail.com\",\n file: \"\",\n hidden: \"hidden\",\n image: \"image.svg\",\n month: \"2025-04\",\n password: \"topsecret\",\n radio: true, // ISSUE: UInput is not supporting boolean values for v-model\n range: 50, // Default value is displayed but not loaded in the v-model\n tel: \"0612345678\",\n time: \"10:49:31\",\n url: \"www.chatgpt.com\",\n week: \"2025-W16\"\n}\n// const state = reactive(items) // Workaround for default-value\n\u003C/script>\n```\n\n### Description\n\nI made a small comparison between `UInput` and other components like `UColorPicker` and `USlider` and I stumbled on a couple of issues.\n* `default-value` is not displayed except for `range` and `USlider`\n* `default-value` is never initialized in the `v-model`\n* Booleans are not supported in the `v-model` and I was therefore not able to make them reactive.\n\nWorkaround is to load the default value via the `state`, but that requires an additional step and is therefore not ideal for dynamic forms\n`const state = reactive(items)`\n\nWorkaround for working with booleans, but I am not sure how to apply the `v-model` yet🤔\n`\u003CUInput v-if=\"typeof state[index] == 'boolean'\" :type=\"index\" :value=\"index\" :checked=\"item\" />`\n\n\n### Additional context\n\nDefault values via `default-value`\n\nDefault value via `state`\n\n\n### Logs\n\n```shell-script\n\n```",[3073,3074],{"name":3020,"color":3021},{"name":3023,"color":3024},3983,"Default values are not loaded in the v-model","2025-06-30T13:04:54Z","https://github.com/nuxt/ui/issues/3983",0.63945365,{"description":3081,"labels":3082,"number":3085,"owner":3029,"repository":3030,"state":3065,"title":3086,"updated_at":3087,"url":3088,"score":3089},"### Environment\n\n- Operating System: Linux\n- Node Version: v24.4.0\n- Nuxt Version: -\n- CLI Version: 3.26.4\n- Nitro Version: -\n- Package Manager: bun@1.2.4\n- Builder: -\n- User Config: -\n- Runtime Modules: -\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nVue\n\n### Version\n\nv3.2.0\n\n### Reproduction\n\nhttps://codesandbox.io/p/devbox/w6mpnq\n\n### Description\n\nThe props `defaultValue` doesn't seem to work on UInput (found this props on the documentation). The field stays empty.\n`modelValue` works \n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3083,3084],{"name":3020,"color":3021},{"name":3023,"color":3024},4569,"defaultValue has no effect","2025-07-22T08:38:57Z","https://github.com/nuxt/ui/issues/4569",0.6405411,{"description":3091,"labels":3092,"number":3098,"owner":3029,"repository":3030,"state":3065,"title":3099,"updated_at":3100,"url":3101,"score":3102},"### Environment\n\n- Operating System: Darwin\n- Node Version: v22.14.0\n- Nuxt Version: 3.17.4\n- CLI Version: 3.25.1\n- Nitro Version: 2.11.12\n- Package Manager: pnpm@10.11.0\n- Builder: -\n- User Config: modules, devtools, css, ui, runtimeConfig, compatibilityDate, dayjs, eslint, image, sanity, supabase\n- Runtime Modules: @nuxt/eslint@1.4.1, @nuxt/ui@3.1.3, @nuxt/image@1.10.0, @nuxtjs/sanity@1.13.3, @nuxtjs/supabase@1.5.1, motion-v/nuxt@0.11.3, dayjs-nuxt@2.1.11, @pinia/nuxt@0.10.1\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.17.4\n\n### Reproduction\n\nHappens also in the Nuxt UI documentation: https://ui.nuxt.com/components/input-menu#items\n\n\n\n### Description\n\nI would expect that all list items appear on the first opening and not on the second one like in following video:\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3093,3094,3097],{"name":3020,"color":3021},{"name":3095,"color":3096},"duplicate","cfd3d7",{"name":3023,"color":3024},4240,"InputMenu shows only seleceted value in the list on first opening","2025-05-28T08:08:48Z","https://github.com/nuxt/ui/issues/4240",0.65193534,{"description":3104,"labels":3105,"number":3109,"owner":3029,"repository":3029,"state":3065,"title":3110,"updated_at":3111,"url":3112,"score":3113},"### 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_",[3106],{"name":3107,"color":3108},"pending triage","E99695",28733,"SelectMenu initial object values","2024-08-28T03:27:34Z","https://github.com/nuxt/nuxt/issues/28733",0.67102903,{"description":3115,"labels":3116,"number":3124,"owner":3029,"repository":3030,"state":3065,"title":3125,"updated_at":3126,"url":3127,"score":3128},"### Environment\n\nOperating System: Linux\r\nNode Version: v20.15.1\r\nNuxt Version: 3.13.0\r\nCLI Version: 3.13.1\r\nNitro Version: 2.9.7\r\nPackage Manager: bun@1.1.27\r\nBuilder: -\r\nUser Config: devtools, extends, modules, ui\r\nRuntime Modules: @nuxt/ui@2.18.4\r\nBuild Modules: -\n\n### Version\n\nv2.18.4\n\n### Reproduction\n\n-\n\n### Description\n\n```\r\nType '{ \"v-model\": string | undefined; icon: string; type: string; size: \"md\"; placeholder: string; autocomplete: string; }' is not assignable to type 'IntrinsicAttributes & Partial\u003C{ name: string; size: InputSize; type: string; required: boolean; class: any; leading: boolean; color: InputColor; ... 16 more ...; modelModifiers: {}; }> & Omit\u003C...>'.\r\n Property 'autocomplete' does not exist on type 'IntrinsicAttributes & Partial\u003C{ name: string; size: InputSize; type: string; required: boolean; class: any; leading: boolean; color: InputColor; ... 16 more ...; modelModifiers: {}; }> & Omit\u003C...>'.\r\n```\n\n### Additional context\n\n`UInput` component doesn't have the default input types (`HTMLInputElement`)\n\n### Logs\n\n_No response_",[3117,3118,3119,3122],{"name":3020,"color":3021},{"name":3026,"color":3027},{"name":3120,"color":3121},"closed-by-bot","ededed",{"name":3123,"color":3121},"stale",2104,"`UInput` default types","2025-06-18T09:06:12Z","https://github.com/nuxt/ui/issues/2104",0.6724687,{"description":3130,"labels":3131,"number":3137,"owner":3029,"repository":3030,"state":3065,"title":3138,"updated_at":3139,"url":3140,"score":3141},"### Environment\n\n- Operating System: Linux\n- Node Version: v22.4.0\n- Nuxt Version: 3.14.1592\n- CLI Version: 3.15.0\n- Nitro Version: 2.10.4\n- Package Manager: pnpm@9.13.2\n- Builder: -\n- User Config: default\n- Runtime Modules: @nuxt/ui@3.0.0-alpha.9, nuxt-auth-sanctum@0.5.2, @vueuse/nuxt@11.3.0\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.14.1592\n\n### Reproduction\n\nHere is my dependencies:\n```json\n \"dependencies\": {\n \"@nuxt/ui\": \"https://pkg.pr.new/@nuxt/ui@59d3375\",\n \"@vueuse/nuxt\": \"^11.3.0\",\n \"nuxt\": \"^3.14.1592\",\n \"nuxt-auth-sanctum\": \"^0.5.2\",\n \"tailwindcss\": \"4.0.0-alpha.34\",\n \"vue\": \"latest\",\n \"vue-router\": \"latest\"\n }\n```\nHere is main template:\n```vue\n\u003Cscript setup lang=\"ts\">\nimport { useDebounceFn } from '@vueuse/core'\n\nconst places = ref([])\nconst placeItems = ref([])\nconst placeOpen = ref(true)\nconst placeLoading = ref(false)\nconst placeSearch = useDebounceFn(async q => {\n if (q.length > 2) {\n placeLoading.value = true\n placeItems.value = await $fetch('http://localhost:85/api/v1/places', { query: { q } })\n placeOpen.value = true\n placeLoading.value = false\n }\n}, 500)\n\u003C/script>\n\n\u003Ctemplate>\n \u003CUFormField label=\"Places\" required>\n \u003CUInputMenu name=\"places\"\n v-model=\"places\"\n v-model:open=\"placeOpen\"\n :items=\"placeItems\"\n :loading=\"placeLoading\"\n :reset-search-term-on-blur=\"false\"\n @focus=\"placeOpen = true\"\n @update:search-term=\"placeSearch\"\n value-key=\"id\"\n label-key=\"name\"\n icon=\"i-lucide-search\"\n placeholder=\"Start typing...\"\n class=\"w-full\"\n multiple\n required />\n \u003C/UFormField>\n\u003C/template>\n```\n[Here](https://skrinshoter.ru/vSpJnffwygq) is video demonstration :)\n\n### Description\n\n`placeOpen.value = true` is not opening dropdown after fetching places.",[3132,3133,3134,3135,3136],{"name":3020,"color":3021},{"name":3023,"color":3024},{"name":3026,"color":3027},{"name":3120,"color":3121},{"name":3123,"color":3121},2724,"UInputMenu property OPEN not working properly","2025-06-18T09:05:39Z","https://github.com/nuxt/ui/issues/2724",0.67566055,["Reactive",3143],{},["Set"],["ShallowReactive",3146],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fjna0dlfQ9fVcVNGc_zBmsq62SZqD9hqiv_3an4t0mzg":-1},"/nuxt/ui/4635"]