``` the ```type=\"text\"``` and ```\u003CUSelect />``` fields match heights, but the ```type=\"search\"``` is the outlier.\n- When NOT using ```\u003CUFormField />```, then the ```type=\"text\"``` field is the outlier. \n\n### Additional context\n\nAs rendered in Dev Tools:\n\n\n\nAfter removing ```type=\"search\"``` in dev tools.\n\n\n\n\n\n### Logs\n\n```shell-script\n\n```",[2887,2888,2889],{"name":2868,"color":2869},{"name":2871,"color":2872},{"name":2874,"color":2875},4014,"Input Fields on ```Safari``` has Mismatched Sizes","2025-04-29T04:28:11Z","https://github.com/nuxt/ui/issues/4014",0.73746735,{"description":2896,"labels":2897,"number":2907,"owner":2877,"repository":2877,"state":2908,"title":2909,"updated_at":2910,"url":2911,"score":2912},"### Environment\n\nnodejs: v18.18.0\r\nnpm: 9.8.1\r\n\"element-plus\": \"^2.8.3\"\r\n\"nuxt\": \"^3.13.2\"\r\n\"@element-plus/nuxt\": \"^1.0.10\"\n\n### Reproduction\n\nlook at Describe the bug\n\n### Describe the bug\n\n\r\nI am sure I have modified this error according to the element ui documentation, but it still reports an error. I saw that element ui has fixed this problem. I am not sure if this problem is related to nuxt. Please check it. Thank you very much.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2898,2901,2904],{"name":2899,"color":2900},"pending triage","E99695",{"name":2902,"color":2903},"needs reproduction","FBCA04",{"name":2905,"color":2906},"possible regression","B90A42",29076,"closed","I encountered a problem when using nuxt3: [el-radio] [API] label act as value is about to be deprecated in version 3.0.0, please use value instead","2024-09-20T03:04:55Z","https://github.com/nuxt/nuxt/issues/29076",0.7005654,{"description":2914,"labels":2915,"number":2924,"owner":2877,"repository":2878,"state":2908,"title":2925,"updated_at":2926,"url":2927,"score":2928},"### Environment\n\nnot needed\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.1.0\n\n### Reproduction\n\nnot needed\n\n### Description\n\nThere is no error state on the input field like color \"error\" when u wrap URadioGroup in UFormField\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2916,2917,2919,2920,2921],{"name":2868,"color":2869},{"name":2902,"color":2918},"CB47CF",{"name":2871,"color":2872},{"name":2874,"color":2875},{"name":2922,"color":2923},"closed-by-bot","ededed",4025,"RedioGroup in Form","2025-05-07T02:09:29Z","https://github.com/nuxt/ui/issues/4025",0.70387363,{"description":2930,"labels":2931,"number":2934,"owner":2877,"repository":2878,"state":2908,"title":2935,"updated_at":2936,"url":2937,"score":2938},"### 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```",[2932,2933],{"name":2868,"color":2869},{"name":2871,"color":2872},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.70404136,{"description":2940,"labels":2941,"number":2945,"owner":2877,"repository":2878,"state":2908,"title":2946,"updated_at":2947,"url":2948,"score":2949},"### Environment\n\n- Operating System: Darwin\n- Node Version: v20.18.3\n- Nuxt Version: 3.16.2\n- CLI Version: 3.24.1\n- Nitro Version: 2.11.9\n- Package Manager: bun@1.1.28\n- Builder: -\n- User Config: devtools, modules, css, future, compatibilityDate\n- Runtime Modules: @nuxt/ui@3.0.2, @nuxt/eslint@1.3.0\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.0.2\n\n### Reproduction\n\nhttps://stackblitz.com/edit/github-s2opq2ko?file=app/pages/index.vue\n\n### Description\n\nGiven this component nesting:\n\n- `UForm`\n - `UModal`\n - `UForm`\n\nThis is rendered as the following html:\n\n- `UForm` -> `form` - ✅\n - `UModal` -> `div` - ✅ (teleported to root)\n - `UForm` -> `div` - ❌ I am expecting `form`.\n\nI couldn't find a mention in the documentation that this is expected behaviour.\n\nTo reproduce:\n1. Run reproduction\n2. Click \"Open modal\" button\n3. Inspect the nested form element. It's a `div`:\n\n\nI am happy to have a crack at a PR, if you're willing to point me in the right direction 😌\n\n\n### Additional context\n\nFor context, this is our use case:\n* User fills out an onboarding form\n* One field in the onboarding form is business details\n* User has option to populate business details via business number (eg. [DUNS](https://www.dnb.com/en-us/smb/duns.html))\n* Business number field open in modal\n* User can enter business number in form in modal\n* User submits form, it populates state in parent form\n\n### Logs\n\n```shell-script\n\n```",[2942,2943,2944],{"name":2868,"color":2869},{"name":2871,"color":2872},{"name":2874,"color":2875},3913,"[Form] Nested `UForm` in `UModal` is not rendered as `form`","2025-04-16T08:34:48Z","https://github.com/nuxt/ui/issues/3913",0.71740836,{"description":2951,"labels":2952,"number":2956,"owner":2877,"repository":2878,"state":2908,"title":2957,"updated_at":2958,"url":2959,"score":2960},"### Environment\n\n- Operating System: Windows \n- Node Version: v20.19.0\n- Nuxt Version: 3.16.2\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.1.1\n\n### Reproduction\n\n- install the latest version `bun add @nuxt/ui@latest`\n- remove cache and node modules `bun nuxi cleanup` `rm .\\node_modules\\`\n- then install `bun install`\n\nIn `nuxt.config.ts` add a custom prefix `{ ui: { prefix: \"Ob\" } } `\nand use the `CheckboxGroup` component as mentioned in docs (and dont forget your custom prefix).\nEx: ` \u003CObCheckboxGroup class=\"bg-red-200\" variant=\"card\" :default-value=\"['System']\" :items=\"items\" />`\n\nFinally run the code and you will see nothing will show.\n\n### Description\n\nI inspected the Dom and noticed `\u003Cucheckbox id=\"v-0-0-0-3-0-0:System\" label=\"System\" disabled=\"false\" value=\"System\">\u003C/ucheckbox>` is being used iterated for all the items. I've then inspected the node modules (\"../node_modules/@nuxt/ui/dist/runtime/components/CheckboxGroup.vue\") for that component after a clean install and saw UCheckbox is being directly used inside the CheckboxGroup component. Inside the node_module component, if i swap out UCheckbox with ObCheckbox, then the code will work as expected. \n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2953,2954,2955],{"name":2868,"color":2869},{"name":2871,"color":2872},{"name":2874,"color":2875},4090,"UCheckboxGroup items don't adhere to the custom prefix","2025-05-06T10:15:57Z","https://github.com/nuxt/ui/issues/4090",0.7210801,{"description":2962,"labels":2963,"number":2971,"owner":2877,"repository":2877,"state":2908,"title":2972,"updated_at":2973,"url":2974,"score":2975},"### Environment\n\nNuxt project info: 15:46:56\r\n\r\n------------------------------\r\n- Operating System: Linux\r\n- Node Version: v16.14.2\r\n- Nuxt Version: 3.5.2\r\n- Nitro Version: 2.4.1\r\n- Package Manager: npm@7.17.0\r\n- Builder: vite\r\n- User Config: -\r\n- Runtime Modules: -\r\n- Build Modules: -\r\n------------------------------\n\n### Reproduction\n\n[reproduction](https://stackblitz.com/github/jbreuil/layout-repro)\r\n\r\nIn this reproduction, the error is triggered when the layout is changed on routing. The error start appearing when adding a ref element in the component. The ref is on a v-for following the [documentation syntax](https://vuejs.org/guide/essentials/template-refs.html#refs-inside-v-for) and [typing](https://vuejs.org/guide/typescript/composition-api.html#typing-template-refs)\n\n### Describe the bug\n\nRelated to #13309, where people have the same error when using Transition.\r\n\r\nHere the error is the same and triggered at the same time (change of layout on routing to another page). In this reproduction, the error is appearing once we add a ref in the v-for of the component.\r\n\r\nFixed if you downgrade to nuxt 3.3.3\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2964,2967,2968],{"name":2965,"color":2966},"3.x","29bc7f",{"name":2899,"color":2900},{"name":2969,"color":2970},"upstream","E8A36D",21323,"Layout error when using an Element ref on v-for","2023-07-06T15:39:03Z","https://github.com/nuxt/nuxt/issues/21323",0.72414416,{"description":2977,"labels":2978,"number":2982,"owner":2877,"repository":2878,"state":2908,"title":2983,"updated_at":2984,"url":2985,"score":2986},"### Environment\n\n```\n- Operating System: `Linux`\n- Node Version: `v23.11.0`\n- Nuxt Version: `3.17.2`\n- CLI Version: `3.25.0`\n- Nitro Version: `2.11.11`\n- Package Manager: `pnpm@10.10.0`\n- Builder: `-`\n- User Config: `devtools`, `modules`, `css`, `future`, `compatibilityDate`\n- Runtime Modules: `@nuxt/ui@3.1.1`, `@nuxt/eslint@1.3.1`\n- Build Modules: `-`\n```\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\n3.17.2\n\n### Reproduction\n\nhttps://codesandbox.io/p/devbox/nuxt-ui3-n3sxks\n\nSample code for fiddling:\n```vue\n\u003Ctemplate>\n \u003CUCard>\n \u003CUFormField>\n \u003CUCheckbox v-model=\"isRtl\" label=\"Right to Left\" />\n \u003C/UFormField>\n \n \u003Cdiv class=\"mt-4 space-y-4 space-x-4\">\n \u003CUFormField label=\"Dynamic Direction Select\">\n \u003CUSelect\n v-model=\"selected\"\n :items=\"items\"\n :dir=\"dir\"\n label=\"Dynamic Direction Select\"\n placeholder=\"Select an option\"\n class=\"w-full max-w-2xl\"\n />\n \u003C/UFormField>\n \n \u003CUFormField label=\"Left to Right\">\n \u003CUSelect\n v-model=\"selected2\"\n :items=\"items\"\n dir=\"ltr\"\n label=\"LTR Select\"\n placeholder=\"Select an option\"\n class=\"w-full max-w-2xl\"\n />\n \u003C/UFormField>\n\n \u003CUFormField label=\"Right to Left\">\n \u003CUSelect\n v-model=\"selected3\"\n :items=\"items\"\n dir=\"rtl\"\n label=\"RTL Select\"\n placeholder=\"Select an option\"\n class=\"w-full max-w-2xl\"\n />\n \u003C/UFormField>\n \u003C/div>\n \u003C/UCard>\n\u003C/template>\n\n\u003Cscript setup>\nconst isRtl = ref(false)\nconst selected = ref('')\nconst selected2 = ref('')\nconst selected3 = ref('')\n\nconst items = [\n 'Item 1',\n 'Item 2',\n 'Item 3',\n 'Item 4',\n 'Item 5',\n 'Item 6',\n 'Item 7',\n]\n\nconst dir = computed(() => isRtl.value ? 'rtl' : 'ltr')\n\u003C/script>\n```\n\n### Description\n\nIt seems `USelect` component ignores the `dir` attribute. This make it inconsistence with the rest of UI components. This issue makes the UI look wierd when localized to RTL languages.\nBoth `\u003CUSelect dir=\"rtl\" ...>` and `\u003CUSelect dir=\"ltr\" ...>` component have `dir=\"ltr\"`.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2979,2980,2981],{"name":2868,"color":2869},{"name":2871,"color":2872},{"name":2874,"color":2875},4131,"USelect ignores dir attribute","2025-05-13T14:10:12Z","https://github.com/nuxt/ui/issues/4131",0.72869205,{"description":2988,"labels":2989,"number":2992,"owner":2877,"repository":2878,"state":2908,"title":2993,"updated_at":2994,"url":2995,"score":2996},"### Environment\n\n- Operating System: Linux\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: app, build, colorMode, compatibilityDate, debug, devtools, fonts, future, hooks, i18n, icon, imports, modules, nitro, routeRules, runtimeConfig, security, ssr, sourcemap, css, telemetry, vite\n- Runtime Modules: @nuxt/eslint@1.3.0, @pinia/nuxt@0.11.0, @vueuse/nuxt@13.1.0, @nuxtjs/i18n@9.5.3, nuxt-security@2.2.0, @nuxt/ui@3.1.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\nhttps://codesandbox.io/p/devbox/epic-smoke-95wysw?file=%2Fapp%2Fpages%2Findex.vue\n\n### Description\n\nUsing the `@update:model-value` event handler produces type errors with the Select component, starting from nuxt-ui v3.1.0 (v3.0.2 works fine).\n\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\nType 'boolean | AcceptableValue | undefined' is not assignable to type '\"yes\" | \"no\"'.\n Type 'undefined' is not assignable to type '\"yes\" | \"no\"'.ts-plugin(2322)\n```",[2990,2991],{"name":2868,"color":2869},{"name":2871,"color":2872},4019,"Type Issue with Select Component","2025-04-29T15:39:56Z","https://github.com/nuxt/ui/issues/4019",0.7336198,["Reactive",2998],{},["Set"],["ShallowReactive",3001],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$frcb11tTLmCKA9srHizIsgEP3pPa67EVH0eZ-2RoU1Xg":-1},"/nuxt/ui/3998"]