\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```",[3202,3203,3205],{"name":3172,"color":3173},{"name":3204,"color":3179},"v3",{"name":3175,"color":3176},4530,"[UInputTags, UInputMenu] Theming behaviour issues","2025-07-15T17:50:02Z","https://github.com/nuxt/ui/issues/4530",0.73048246,{"description":3212,"labels":3213,"number":3216,"owner":3181,"repository":3182,"state":3217,"title":3218,"updated_at":3219,"url":3220,"score":3221},"### 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```",[3214,3215],{"name":3172,"color":3173},{"name":3204,"color":3179},4569,"closed","defaultValue has no effect","2025-07-22T08:38:57Z","https://github.com/nuxt/ui/issues/4569",0.6941323,{"description":3223,"labels":3224,"number":3227,"owner":3181,"repository":3182,"state":3217,"title":3228,"updated_at":3229,"url":3230,"score":3231},"### Environment\n\n- Operating System: Darwin\n- Node Version: v22.17.1\n- Nuxt Version: 4.0.2\n- CLI Version: 3.27.0\n- Nitro Version: 2.12.4\n- Package Manager: npm@11.5.2\n- Builder: -\n- User Config: compatibilityDate, site, modules, supabase, devtools, css, content, nitro, icon, devServer, runtimeConfig, llms, routeRules\n- Runtime Modules: @nuxt/image@1.11.0, @nuxt/ui-pro@3.3.0, @nuxt/content@3.6.3, nuxt-og-image@5.1.9, nuxt-llms@0.1.3, @nuxtjs/supabase@1.6.0, @pinia/nuxt@0.11.2, pinia-plugin-persistedstate/nuxt@4.4.1\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv4.0.2\n\n### Reproduction\n\n/\n\n### Description\n\npassing \n\n```ts\n\u003CLazyUContentSearch\n :ui=\"{ modal: 'test-class' }\"\n>\n```\n\nis not working\n\nbut the following does work\n\n```ts\nexport default defineAppConfig({\n uiPro: {\n contentSearch: {\n slots: {\n modal: 'test-class',\n },\n },\n },\n})\n```\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3225,3226],{"name":3172,"color":3173},{"name":3204,"color":3179},4673,"ui prop not working for UContentSearch","2025-08-07T09:35:15Z","https://github.com/nuxt/ui/issues/4673",0.7175361,{"description":3233,"labels":3234,"number":3239,"owner":3181,"repository":3182,"state":3217,"title":3240,"updated_at":3241,"url":3242,"score":3243},"### Description\n\nHello,\n\nIs it possible to have a props to set the rounded class for the Avatar in Nuxt UI v4\n\nI mean having the possibility to use rounded-lg, etc\n\nIt's possible to have it like that but maybe a prop can be appropriate\n\n```\n:ui=\"{\n root: 'rounded-lg',\n}\"\n```\nRegards,\n\n",[3235,3238],{"name":3236,"color":3237},"enhancement","a2eeef",{"name":3175,"color":3176},4807,"Avatar with rounded-X instead of rounded-full","2025-08-22T11:42:48Z","https://github.com/nuxt/ui/issues/4807",0.71936166,{"description":3245,"labels":3246,"number":3250,"owner":3181,"repository":3182,"state":3217,"title":3251,"updated_at":3252,"url":3253,"score":3254},"### Environment\n\n- Operating System: Darwin\n- Node Version: v24.7.0\n- Nuxt Version: 4.1.1\n- CLI Version: 3.28.0\n- Nitro Version: 2.12.5\n- Package Manager: pnpm@10.15.1\n- Builder: -\n- User Config: modules, compatibilityDate, devtools, css, vite\n- Runtime Modules: @nuxt/ui@4.0.0-alpha.1\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Package\n\nv4.0.0-alpha.x\n\n### Version\n\nv4.0.0-alpha.1\n\n### Reproduction\n\nhttps://github.com/adjabaev/motion-v-201-reprod/tree/main/app\n\n### Description\n\nhttps://github.com/motiondivision/motion-vue/issues/201\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3247,3248,3249],{"name":3172,"color":3173},{"name":3175,"color":3176},{"name":3178,"color":3179},4929,"UIcon has a SSR Issue","2025-09-12T18:14:15Z","https://github.com/nuxt/ui/issues/4929",0.7237653,{"description":3256,"labels":3257,"number":3262,"owner":3181,"repository":3181,"state":3217,"title":3263,"updated_at":3264,"url":3265,"score":3266},"### Environment\n\n- Operating System: Linux\r\n- Node Version: v20.6.1\r\n- Nuxt Version: 3.9.1\r\n- CLI Version: 3.10.0\r\n- Nitro Version: 2.8.1\r\n- Package Manager: npm@9.8.1\r\n- Builder: -\r\n- User Config: devtools\r\n- Runtime Modules: -\r\n- Build Modules: -\n\n### Reproduction\n\nAdd this to an existing project or create a new project...\r\n\r\n```\r\n\u003Ctemplate>\r\n \u003Cdiv>\r\n \u003Ca href=\"https://nuxt.com/\" :target=\"linkTarget\" ref=\"link\"> nuxt.com \u003C/a>\r\n \u003Cdl>\r\n \u003Cdt>expected\u003C/dt>\r\n \u003Cdd>{{ linkTarget }}\u003C/dd>\r\n \u003Cdt>actual\u003C/dt>\r\n \u003Cdd>{{ $refs.link?.target }}\u003C/dd>\r\n \u003C/dl>\r\n \u003C/div>\r\n\u003C/template>\r\n\r\n\u003Cscript lang=\"ts\" setup>\r\nconst linkTarget = computed(() => (process.server ? \"server\" : \"client\"));\r\n\u003C/script>\r\n```\n\n### Describe the bug\n\nWhen the server generates a value, in this case \"server\" ... and when the client hydrates and changes the value, in this case to \"client\", the hydration doesn't update the value passed to component props. However if the value is changed to anything other than the two values then it picks up the change immediately.\n\n### Additional context\n\nIn my actual case I was using the [@vueuse/useMediaQuery](https://vueuse.org/core/useMediaQuery/) composable to set a prop based on screensize. On server it would always default to \"mobile\" because it doesn't have access to the screen size, however if you loaded it on a larger screen (like a desktop or laptop) it would get a different value. Resizing the screen would have no effect until it went into the \"mobile\" threshold, and then back out of it.\n\n### Logs\n\n_No response_",[3258,3261],{"name":3259,"color":3260},"3.x","29bc7f",{"name":3192,"color":3193},25183,"When a prop has two possible values and the server sets one, and the client sets the other it loses initial reactivity to other props","2024-01-13T00:59:38Z","https://github.com/nuxt/nuxt/issues/25183",0.7255453,{"description":3268,"labels":3269,"number":3273,"owner":3181,"repository":3182,"state":3217,"title":3274,"updated_at":3275,"url":3276,"score":3277},"### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Package\n\nv4.x\n\n### Version\n\nv4.0.1\n\n### Reproduction\n\n- https://s5gnp7-3000.csb.app/\n- https://codesandbox.io/p/devbox/determined-feynman-s5gnp7?file=%2Fapp%2Fapp.vue%3A129%2C51&workspaceId=ws_5t1C1ubVCgW2ZXzyDhJCyH\n\n### Description\n\n`\u003CUDashboardSidebar side=\"right\">` has no effect. The sidebar is still left and opens from the left on mobile.\n\nThe only effect it has, is that it has no more `border-r` class\n",[3270,3271,3272],{"name":3172,"color":3173},{"name":3175,"color":3176},{"name":3178,"color":3179},5135,"DashboardSidebar prop side=\"right\" has no effect","2025-10-06T10:41:22Z","https://github.com/nuxt/ui/issues/5135",0.72627276,{"description":3279,"labels":3280,"number":3283,"owner":3181,"repository":3182,"state":3217,"title":3284,"updated_at":3285,"url":3286,"score":3287},"### Environment\n\n------------------------------\n- Operating System: Linux\n- Node Version: v20.19.1\n- Nuxt Version: 3.17.5\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, css, future, compatibilityDate, vite\n- Runtime Modules: @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.1.3\n\n### Reproduction\n\nhttps://stackblitz.com/edit/nuxt-starter-bsi7gjhw?file=app%2Fapp.vue\n\n### Description\n\nThe UInput component behaves the same way whether using `v-model` or just `:modelValue`—it retains input values when typed into. However, this is incorrect because I did not set up the `@update:modelValue` event\n\n\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3281,3282],{"name":3172,"color":3173},{"name":3204,"color":3179},4355,"The UInput component is not a controlled component","2025-06-16T10:45:31Z","https://github.com/nuxt/ui/issues/4355",0.72811836,["Reactive",3289],{},["Set"],["ShallowReactive",3292],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fMC3o0YPrfvQehpvOp2OkpnX8-u92c7AzuKCjw4CV3A0":-1},"/nuxt/ui/4691"]