``` 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```",[3018,3021,3024],{"name":3019,"color":3020},"bug","d73a4a",{"name":3022,"color":3023},"v3","49DCB8",{"name":3025,"color":3026},"triage","ffffff",4014,"nuxt","ui","open","Input Fields on ```Safari``` has Mismatched Sizes","2025-04-29T04:28:11Z","https://github.com/nuxt/ui/issues/4014",0.65121067,{"description":3036,"labels":3037,"number":3041,"owner":3028,"repository":3029,"state":3030,"title":3042,"updated_at":3043,"url":3044,"score":3045},"### Environment\n\nThe default input fields when used on small devices (Like my iPhone 12 mini) seemingly render text below 16px causing the browser to zoom when clicking an input field. This doesn't happen on my larger devices as presumably the text renders above 16px.\n\nMight be good to force a minimum text size of 16px to avoid this default behaviour as the workaround otherwise is to override that zoom behaviour, but that could impact accessibility unless the user zooms in manually with their fingers.\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3\n\n### Reproduction\n\nhttps://ui.nuxt.com/components/input happens on the official site too for example here on my iPhone 12 mini\n\n### Description\n\ninput field text renders below recommended 16px on small devices causing the screen to zoom when clicking input fields. This occurs on input fields smaller than xl. Granted in my opinion the text looks plenty big at medium and large size but those cause the screen zoom by default\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3038,3039,3040],{"name":3019,"color":3020},{"name":3022,"color":3023},{"name":3025,"color":3026},4117,"Default text size on input fields too small on small devices causing zoom when clicked (sub 16px?)","2025-05-10T18:34:49Z","https://github.com/nuxt/ui/issues/4117",0.6963844,{"description":3047,"labels":3048,"number":3052,"owner":3028,"repository":3029,"state":3030,"title":3053,"updated_at":3054,"url":3055,"score":3056},"### Environment\n\n- Browser: Safari 18.3\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.1.3\n\n### Reproduction\n\n## Nuxt UI Website\nhttps://github.com/user-attachments/assets/cba84f65-4c8f-4398-ae34-d2844b2ad767\n\n## My Project\nhttps://github.com/user-attachments/assets/7a88b397-14dc-4150-b396-7e1fbd1a0b7e\n\nThis by the way is not happening with the `UTabs` Example shown in the documentation.\n\n## Documentation\nhttps://github.com/user-attachments/assets/9432385f-141b-4d58-bf28-af2a68833dae\n\n### Description\n\nOn Safari (tested with 18.3) `UTabs` is flickering when switching tabs. Since this also happens on the Nuxt UI Webpage I have not created a minimal reproduction.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3049,3050,3051],{"name":3019,"color":3020},{"name":3022,"color":3023},{"name":3025,"color":3026},4280,"`UTabs` trigger flickers when switching tabs (Safari-only)","2025-06-02T13:28:06Z","https://github.com/nuxt/ui/issues/4280",0.7271604,{"description":3058,"labels":3059,"number":3063,"owner":3028,"repository":3029,"state":3064,"title":3065,"updated_at":3066,"url":3067,"score":3068},"### 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```",[3060,3061,3062],{"name":3019,"color":3020},{"name":3022,"color":3023},{"name":3025,"color":3026},3913,"closed","[Form] Nested `UForm` in `UModal` is not rendered as `form`","2025-04-16T08:34:48Z","https://github.com/nuxt/ui/issues/3913",0.6935897,{"description":3070,"labels":3071,"number":3080,"owner":3028,"repository":3029,"state":3064,"title":3081,"updated_at":3082,"url":3083,"score":3084},"### Environment\n\n- Operating System: Darwin\n- Node Version: v22.14.0\n- Nuxt Version: 3.17.0\n- CLI Version: 3.25.0\n- Nitro Version: 2.11.11\n- Package Manager: pnpm@10.9.0\n- Builder: -\n- User Config: modules, colorMode, image, content, plausible, devtools, hub, css, mdc, nitro, runtimeConfig, routeRules, future, compatibilityDate, eslint\n- Runtime Modules: @nuxt/eslint@1.3.0, @nuxt/image@1.10.0, @nuxt/ui-pro@3.1.0, @nuxt/content@3.5.1, @nuxthub/core@0.8.25, @nuxtjs/plausible@1.2.0, @vueuse/nuxt@13.1.0, nuxt-og-image@5.1.3\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\n1. Open [saas-template.nuxt.dev](https://saas-template.nuxt.dev/) in Safari on macOS 18.4.\n2. Scroll to the Testimonials section.\n3. Observe that after a line break in the grid, the first card in each new row is not rendered.\n4. Open Safari’s developer tools and disable the first CSS rule:\n```\n:is(.*:will-change-transform>*) {\n will-change: transform;\n}\n```\n5. Observe that the missing cards now appear, but borders render incorrectly.\n\n\n### Description\n\nOn Safari for macOS (Version 18.4 – 20621.1.15.11.10), using @nuxt/ui components in a responsive grid layout causes elements to disappear after a line break. Specifically, the first item in each new row is not rendered when will-change: transform is applied.\n\n**🔍 Context**\nThe issue is reproducible on your official SaaS template: [saas-template.nuxt.dev](https://saas-template.nuxt.dev/), in the testimonial section. This section uses only @nuxt/ui components – no @nuxt/ui-pro components are involved. The relevant code lives in [/app/pages/index.vue](https://github.com/nuxt-ui-pro/saas/blob/main/app/pages/index.vue), lines 58–80.\n\n**📍 Suspected Source**\nIn Safari, the following rule seems to break the layout:\n\n```\n:is(.*:will-change-transform>*) {\n will-change: transform;\n}\n```\nDisabling this rule in Safari's dev tools makes the hidden items visible again. However, doing so causes border-top rendering to break.\n\n\n**📸 Screenshots**\nIssue (first items not rendered):\n\n\nAfter disabling will-change (cards reappear):\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3072,3073,3076,3077],{"name":3019,"color":3020},{"name":3074,"color":3075},"duplicate","cfd3d7",{"name":3022,"color":3023},{"name":3078,"color":3079},"pro","5BD3CB",4026,"Safari Bug: Grid layout issues with `will-change: transform`","2025-04-30T13:51:05Z","https://github.com/nuxt/ui/issues/4026",0.6988483,{"description":3086,"labels":3087,"number":3097,"owner":3028,"repository":3028,"state":3064,"title":3098,"updated_at":3099,"url":3100,"score":3101},"### Environment\r\n\r\n 2.15.8\r\n\r\n### Reproduction\r\n\r\n2.15.8\r\n\r\n### Describe the bug\r\n\r\nIn my Nuxt js app on production server i am getting issue with safari browser both on desktop and mobile view on initial load. i am using Nuxt version 2.15.8. On initial load safari browser is giving errors and not applying search on button click and returning these errors (see log) . When refresh the page it works fine, but not on the initial load. \r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n### Logs\r\n\r\n```shell-script\r\nSyntaxError: Unexpected identifier 'lValue'. Expected an opening '(' before a function's parameter list\r\nSyntaxError: Unexpected identifier 'y'. Expected an opening '(' before a function's parameter list.\r\n```\r\n",[3088,3091,3094],{"name":3089,"color":3090},"pending triage","E99695",{"name":3092,"color":3093},"2.x","d4c5f9",{"name":3095,"color":3096},"needs reproduction","FBCA04",22172,"On initial load safari browser is giving errors","2024-01-16T11:34:13Z","https://github.com/nuxt/nuxt/issues/22172",0.71099323,{"description":3103,"labels":3104,"number":3113,"owner":3028,"repository":3029,"state":3064,"title":3114,"updated_at":3115,"url":3116,"score":3117},"### 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```",[3105,3106,3108,3109,3110],{"name":3019,"color":3020},{"name":3095,"color":3107},"CB47CF",{"name":3022,"color":3023},{"name":3025,"color":3026},{"name":3111,"color":3112},"closed-by-bot","ededed",4025,"RedioGroup in Form","2025-05-07T02:09:29Z","https://github.com/nuxt/ui/issues/4025",0.71626484,{"description":3119,"labels":3120,"number":3126,"owner":3028,"repository":3029,"state":3064,"title":3127,"updated_at":3128,"url":3129,"score":3130},"### 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```",[3121,3122,3123,3124,3125],{"name":3019,"color":3020},{"name":3095,"color":3107},{"name":3022,"color":3023},{"name":3025,"color":3026},{"name":3111,"color":3112},4103,"InputMenu Event onChange","2025-05-17T02:08:14Z","https://github.com/nuxt/ui/issues/4103",0.7196428,{"description":3132,"labels":3133,"number":3138,"owner":3028,"repository":3029,"state":3064,"title":3139,"updated_at":3140,"url":3141,"score":3142},"### Environment\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: npm@10.9.2\n- Builder: -\n- User Config: modules, compatibilityDate, devtools, css, ui, devServer, future, telemetry, hooks, eslint\n- Runtime Modules: @nuxt/eslint@0.6.2, @nuxt/ui-pro@3.0.1, nuxt-jsonld@2.1.0, @pinia/nuxt@0.10.1\n- Build Modules: -\n\n\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nNuxt v3.16.1\nui-pro v3.0.1\n\n### Reproduction\n\nWhen I add the following to my nuxt.config.ts:\n\n```ts\n{\n ui: {\n colorMode: false\n }\n}\n```\n\n...then `npx nuxi typecheck` fails with 8 errors.\n\n```\n[...snip]\nnode_modules/@nuxt/ui-pro/dist/runtime/vue/components/ColorModeButton.vue:18:24 - error TS2305: Module '\"#imports\"' has no exported member 'useColorMode'.\n\n18 import { useAppConfig, useColorMode } from '#imports'\n ~~~~~~~~~~~~\n\nnode_modules/@nuxt/ui-pro/dist/runtime/vue/components/ColorModeSelect.vue:10:24 - error TS2305: Module '\"#imports\"' has no exported member 'useColorMode'.\n\n10 import { useAppConfig, useColorMode } from '#imports'\n ~~~~~~~~~~~~\n\nnode_modules/@nuxt/ui-pro/dist/runtime/vue/components/ColorModeSwitch.vue:10:24 - error TS2305: Module '\"#imports\"' has no exported member 'useColorMode'.\n\n10 import { useAppConfig, useColorMode } from '#imports'\n ~~~~~~~~~~~~\n\n\nFound 8 errors in 8 files.\n\nErrors Files\n 1 node_modules/@nuxt/ui-pro/dist/runtime/components/color-mode/ColorModeButton.vue:18\n 1 node_modules/@nuxt/ui-pro/dist/runtime/components/color-mode/ColorModeSelect.vue:10\n 1 node_modules/@nuxt/ui-pro/dist/runtime/components/color-mode/ColorModeSwitch.vue:10\n 1 node_modules/@nuxt/ui-pro/dist/runtime/components/content/ContentSearch.vue:89\n 1 node_modules/@nuxt/ui-pro/dist/runtime/components/DashboardSearch.vue:57\n 1 node_modules/@nuxt/ui-pro/dist/runtime/vue/components/ColorModeButton.vue:18\n 1 node_modules/@nuxt/ui-pro/dist/runtime/vue/components/ColorModeSelect.vue:10\n 1 node_modules/@nuxt/ui-pro/dist/runtime/vue/components/ColorModeSwitch.vue:10\n\n ERROR Process exited with non-zero status (2)\n```\n\n### Description\n\nI think that there probably needs to be a stub export set up in all cases? Or these files should not be gathered by the typechecking script?\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3134,3135,3136,3137],{"name":3019,"color":3020},{"name":3022,"color":3023},{"name":3078,"color":3079},{"name":3025,"color":3026},3657,"Setting ui.colorMode = false breaks nuxi typecheck","2025-03-27T20:54:57Z","https://github.com/nuxt/ui/issues/3657",0.72381485,{"description":3144,"labels":3145,"number":3149,"owner":3028,"repository":3029,"state":3064,"title":3150,"updated_at":3151,"url":3152,"score":3153},"### Environment\n\nN/A\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.2.0\n\n### Reproduction\n\nhttps://codesandbox.io/p/devbox/compassionate-jasper-w2k3lm\n\n### Description\n\nThe `InputMenu` component throws an error if one of the fields provided in `filterFields` resolved to a nullish or non-string value. You can reproduce this in the sandbox by typing in the input box and observing the console.\n\nSo having the following setup errors out, which is a real-world use case I'm encountering this:\n\n```vue\n\u003Cscript lang=\"ts\" setup>\nconst items = [\n {\n label: 'foo',\n alias: 'something'\n },\n {\n label: 'bar'\n }\n]\n\u003C/script>\n\n\u003Ctemplate>\n \u003CUInputMenu :items :filter-fields=\"['label', 'alias']\" />\n\u003C/template>\n```\n\nThis is caused by `useFilter.contains` being called with a non-string value.\n\nIt is somewhat related to https://github.com/nuxt/ui/issues/3606 which has been addressed previously, but only for primitive item types.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3146,3147,3148],{"name":3019,"color":3020},{"name":3022,"color":3023},{"name":3025,"color":3026},4509,"InputMenu: error if field field is nullish or non-string","2025-07-12T10:15:32Z","https://github.com/nuxt/ui/issues/4509",0.7261386,["Reactive",3155],{},["Set"],["ShallowReactive",3158],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fmIwiM5ifTua-YeR_2h-kPI7BQS0aVtwEwX-q1Kpu-xg":-1},"/nuxt/ui/4281"]