\n```\n\n### Will results something like this\n```html\n\u003Cdiv class=\"... root-test base-test\">\n ...\n \u003Cinput class=\"...\" />\n\u003C/div>\n```\n\n### Description\n\nWhen applying themes in `app.config.ts`, both **UInputTags** and **UInputMenu (multiple)** share the same weird behaviour compared with other components, where the class applied to `base` part of the component are applied to `root` part of the component.\n\n### Expected Behaviour\nThe applied class on `base` should be applied to the `\u003Cinput />`, not the `root` part of the component which is the outer `\u003Cdiv />` just like other input components such as **UInput**, **UInputNumber**, or **UTextarea**.\n\nCorrect me if I'm wrong if this are intended, thank you!\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3169,3170,3171],{"name":3140,"color":3141},{"name":3158,"color":3159},{"name":3143,"color":3144},4530,"[UInputTags, UInputMenu] Theming behaviour issues","2025-07-15T17:50:02Z","https://github.com/nuxt/ui/issues/4530",0.736969,{"description":3178,"labels":3179,"number":3188,"owner":3146,"repository":3147,"state":3189,"title":3190,"updated_at":3191,"url":3192,"score":3193},"### Environment\n\n- Operating System: `Darwin`\n- Node Version: `v22.14.0`\n- Nuxt Version: `3.16.2`\n- CLI Version: `3.25.0`\n- Nitro Version: `2.11.9`\n- Package Manager: `pnpm@10.9.0`\n- Builder: `-`\n- User Config: `modules`, `devtools`, `css`, `devServer`, `content`, `future`, `compatibilityDate`, `nitro`, `eslint`, `icon`, `llms`\n- Runtime Modules: `@nuxt/eslint@1.3.0`, `@nuxt/image@1.10.0`, `@nuxt/ui-pro@3.1.0`, `@nuxt/content@3.5.1`, `nuxt-og-image@5.1.2`, `nuxt-llms@0.1.2`\n- Build Modules: `-`\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### UI Version\n\nv3.1.0\n\n### Safari Version\n\nv18.5 (20621.2.5.11.5)\n\n### Reproduction\n\n[https://github.com/saltytostitos/ui-docs-input-type-search](https://github.com/saltytostitos/ui-docs-input-type-search)\n\nRepro using UI Pro Docs Template [https://github.com/nuxt-ui-pro/docs/tree/main](https://github.com/nuxt-ui-pro/docs/tree/main)\n\n### Description\n\nInput/Select sizes do not match on Safari Desktop. \n\n\n\nThey seem to match on Chrome.\n\n\n\nAs shown, the Tailwind Only fields work correctly (using same css classes).\n\nObservations:\n- Oddly enough, when using ```\u003CUFormField />``` 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```",[3180,3181,3182,3183,3186],{"name":3140,"color":3141},{"name":3158,"color":3159},{"name":3143,"color":3144},{"name":3184,"color":3185},"closed-by-bot","ededed",{"name":3187,"color":3185},"stale",4014,"closed","Input Fields on ```Safari``` has Mismatched Sizes","2025-08-20T02:08:51Z","https://github.com/nuxt/ui/issues/4014",0.70054436,{"description":3195,"labels":3196,"number":3200,"owner":3146,"repository":3146,"state":3189,"title":3201,"updated_at":3202,"url":3203,"score":3204},"When I wrote the template, some strings (such as string: 2016200202, but string: 201620020 but no problem) could not be rendered on the server side,.\r\nnuxt: 1.2.1,\r\nvue: 2.5.13\r\nThe test code:\r\n\r\n`\u003Ctemplate>`\r\n `\u003Cdiv class='container'>`\r\n`\u003Cdiv>2016200202\u003C/div>`\r\n `\u003C/div>`\r\n`\u003C/template>`\r\n\r\nThe following error message:\r\n[Vue warn]: The client-side rendered virtual DOM tree is not matching server-rendered content. This is likely caused by incorrect HTML markup, for example nesting block-level elements inside \u003Cp>, or missing \u003Ctbody>. Bailing hydration and performing full client-side render.\n\n\u003C!--cmty-->\u003C!--cmty_prevent_hook-->\n\u003Cdiv align=\"right\">\u003Csub>\u003Cem>This question is available on \u003Ca href=\"https://nuxtjs.cmty.io\">Nuxt.js\u003C/a> community (\u003Ca href=\"https://nuxtjs.cmty.io/nuxt/nuxt.js/issues/c2348\">#c2348\u003C/a>)\u003C/em>\u003C/sub>\u003C/div>",[3197],{"name":3198,"color":3199},"2.x","d4c5f9",2702,"Some of the strings on ios 10 safari are rendering errors on the server side, which is weird.","2023-01-18T16:02:30Z","https://github.com/nuxt/nuxt/issues/2702",0.70830566,{"description":3206,"labels":3207,"number":3211,"owner":3146,"repository":3147,"state":3189,"title":3212,"updated_at":3213,"url":3214,"score":3215},"### Environment\n\nNuxtUI : 3.1.1\nNuxt: 3.17.0\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.17.0\n\n### Reproduction\n\nhttps://ui.nuxt.com/components/calendar#color\n\n### Description\n\n\u003Cimg width=\"933\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/8cbd8604-5bc2-4155-8136-f799f00fa693\" />",[3208,3209,3210],{"name":3140,"color":3141},{"name":3158,"color":3159},{"name":3143,"color":3144},4084,"Incorrect display of \"Today\" in the calendar","2025-05-06T15:36:48Z","https://github.com/nuxt/ui/issues/4084",0.7147452,{"description":3217,"labels":3218,"number":3231,"owner":3146,"repository":3146,"state":3189,"title":3232,"updated_at":3233,"url":3234,"score":3235},"### Environment\n\n- Operating System: `Darwin`\r\n- Node Version: `v18.12.1`\r\n- Nuxt Version: `3.0.0`\r\n- Nitro Version: `1.0.0`\r\n- Package Manager: `yarn@3.2.3`\r\n- Builder: `vite`\r\n- User Config: `app`, `modules`, `typescript`, `runtimeConfig`\r\n- Runtime Modules: `@nuxtjs/tailwindcss@6.1.3`, `nuxt-icon@0.1.8`\r\n- Build Modules: `-`\n\n### Reproduction\n\nhttps://stackblitz.com/edit/github-zk2q2e?file=app.vue\r\n\r\nAlthough typechecks in stackblitz does not work for me (I'm a first time user)\n\n### Describe the bug\n\nWhen returning a `Date` from an api route, the `Date` becomes a `string` (because `json` does not support `Date`). However, the type is still `Date` when using `useFetch`. When using typescript in strict mode this discrepancy makes it unusable.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[3219,3222,3225,3228],{"name":3220,"color":3221},"3.x","29bc7f",{"name":3223,"color":3224},"workaround available","11376d",{"name":3226,"color":3227},"nitro","bfd4f2",{"name":3229,"color":3230},"upstream","E8A36D",15590,"Date type remains after json serialization, causing problems in typescript strict mode","2023-01-24T13:59:56Z","https://github.com/nuxt/nuxt/issues/15590",0.7211276,{"description":3237,"labels":3238,"number":3242,"owner":3146,"repository":3147,"state":3189,"title":3243,"updated_at":3244,"url":3245,"score":3246},"### Environment\n\n- Operating System: Linux\n- Node Version: v20.12.0\n- Nuxt Version: 3.17.3\n- CLI Version: 3.25.1\n- Nitro Version: 2.11.12\n- Package Manager: pnpm@8.15.6\n- Builder: -\n- User Config: modules, devtools, compatibilityDate, future, css\n- Runtime Modules: @nuxt/ui@3.1.1\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\n3.2.0\n\n### Reproduction\n\nhttps://codesandbox.io/p/devbox/pensive-spence-mtw49s\n\n### Description\n\nThe `title` attribute works. But Typescript is not happy.\n\n\u003Cimg width=\"1300\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/37005c53-d229-476c-b287-1578fc517c64\" />\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3239,3240,3241],{"name":3140,"color":3141},{"name":3158,"color":3159},{"name":3143,"color":3144},4407,"SelectInput search-input props has typescript errors with native input attributes","2025-07-12T12:31:08Z","https://github.com/nuxt/ui/issues/4407",0.72439396,{"description":3248,"labels":3249,"number":3251,"owner":3146,"repository":3146,"state":3189,"title":3252,"updated_at":3253,"url":3254,"score":3255},"So a bit of an odd-ball one here, and not sure the title is perfectly correct. I've set up a bare-bones sample repo that is showing this issue as well as put it up on Netlify.\r\n\r\nElement-UI is a UI toolkit for Vue 2, and I'm seeing some very odd behaviour when using within a Nuxtjs project. I think it's Nuxtjs specific issue (used components within other apps fine) but if you think otherwise I'll also open a ticket over in their repo too!\r\n\r\nThe GIF show's it best, but as you can see when I open the date picker, the `head` goes through a number of weird changes (`title` changes, `meta` tags disappear) and never resets itself. Are they doing something weird or is Nuxtjs not handling the DOM changes they do?\r\n\r\n[GIF recording](https://cl.ly/kJau)\r\n[Sample repo](https://github.com/mikhailbot/elementui-test)\r\n[Sample website](https://janitor-rose-25820.netlify.com)\r\n\r\nNuxtjs: 0.10.6 (latest from `vue init nuxt/starter`)\r\nNode: 6.10.2/7.10.0\r\nElementUI: 1.2.9\r\nBrowser/OS: MacOS 10.11+ on Chrome 56+ and Safari 10, Windows 10 on Chrome 56+, Mobile Safari on iOS 10.3\n\n\u003C!--cmty-->\u003C!--cmty_prevent_hook-->\n\u003Cdiv align=\"right\">\u003Csub>\u003Cem>This question is available on \u003Ca href=\"https://nuxtjs.cmty.io\">Nuxt.js\u003C/a> community (\u003Ca href=\"https://nuxtjs.cmty.io/nuxt/nuxt.js/issues/c573\">#c573\u003C/a>)\u003C/em>\u003C/sub>\u003C/div>",[3250],{"name":3198,"color":3199},664,"ElementUI Vue Components Rendering Issues","2023-01-18T15:39:39Z","https://github.com/nuxt/nuxt/issues/664",0.72861683,{"labels":3257,"number":3265,"owner":3146,"repository":3146,"state":3189,"title":3266,"updated_at":3267,"url":3268,"score":3269},[3258,3259,3262],{"name":3220,"color":3221},{"name":3260,"color":3261},"pending triage","E99695",{"name":3263,"color":3264},"needs reproduction","FBCA04",23460,"TS Typing issue.","2023-10-20T22:22:28Z","https://github.com/nuxt/nuxt/issues/23460",0.7349684,["Reactive",3271],{},["Set"],["ShallowReactive",3274],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fsTJEGGLZtKFZTe5_8wR9HJ1lOdmGwJq9D3QUftavric":-1},"/nuxt/ui/4712"]