\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```",[3181,3182,3183],{"name":3140,"color":3141},{"name":3143,"color":3144},{"name":3146,"color":3147},4530,"[UInputTags, UInputMenu] Theming behaviour issues","2025-07-15T17:50:02Z","https://github.com/nuxt/ui/issues/4530",0.6877606,{"description":3190,"labels":3191,"number":3197,"owner":3149,"repository":3150,"state":3198,"title":3199,"updated_at":3200,"url":3201,"score":3202},"### Environment\n\n- Operating System: `Windows_NT`\n- Node Version: `v22.13.1`\n- Nuxt Version: `3.17.2`\n- CLI Version: `3.25.0`\n- Nitro Version: `2.11.11`\n- Package Manager: `yarn@1.22.22`\n- Builder: `-`\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\n3.1.1\n\n### Reproduction\n\nhttps://github.com/user-attachments/assets/3204c1e4-c367-4397-b3fc-7a8c335bf000\n\n### Description\n\nCheck current docs. https://ui.nuxt.com/components/input-menu#items\n\n### Additional context\n\nWhen clicking on the dropdown the first time not all items are shown. When clicking the second time the items are all there.\n\n### Logs\n\n```shell-script\n\n```",[3192,3193,3196],{"name":3140,"color":3141},{"name":3194,"color":3195},"duplicate","cfd3d7",{"name":3143,"color":3144},4100,"closed","InputMenu: Not all items shown in dropdown on first open","2025-05-07T14:53:25Z","https://github.com/nuxt/ui/issues/4100",0.62704194,{"description":3204,"labels":3205,"number":3209,"owner":3149,"repository":3150,"state":3198,"title":3210,"updated_at":3211,"url":3212,"score":3213},"### Environment\n\n- Operating System: `Darwin`\n- Node Version: `v22.14.0`\n- Nuxt Version: `4.0.3`\n- CLI Version: `3.28.0`\n- Nitro Version: `2.12.4`\n- Package Manager: `pnpm@10.9.0`\n- Builder: `-`\n- User Config: `compatibilityDate`, `devtools`, `extends`, `components`, `alias`, `dir`, `ssr`, `modules`, `ui`, `css`, `imports`, `app`, `runtimeConfig`\n- Runtime Modules: `@nuxt/ui@3.3.2`, `@pinia/nuxt@0.11.2`, `@vueuse/nuxt@13.6.0`\n- Build Modules: `-`\n\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.3.2\n\n### Reproduction\n\nhttps://codesandbox.io/p/devbox/fancy-leaf-5z2y85\n\n### Description\n\nThe InputMenu component crashes when provided with numeric values in its items prop, the same usage works correctly with SelectMenu.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3206,3207,3208],{"name":3140,"color":3141},{"name":3143,"color":3144},{"name":3146,"color":3147},4767,"InputMenu crashes when using numeric items","2025-08-16T02:41:48Z","https://github.com/nuxt/ui/issues/4767",0.64301515,{"description":3215,"labels":3216,"number":3219,"owner":3149,"repository":3150,"state":3198,"title":3220,"updated_at":3221,"url":3222,"score":3223},"### Environment\n\n- Operating System: `Darwin`\n- Node Version: `v22.14.0`\n- Nuxt Version: `3.18.0`\n- CLI Version: `3.27.0`\n- Nitro Version: `2.12.4`\n- Package Manager: `pnpm@10.12.3`\n- Builder: `-`\n- User Config: `modules`, `ssr`, `components`, `devtools`, `app`, `css`, `colorMode`, `runtimeConfig`, `future`, `experimental`, `compatibilityDate`, `eslint`, `fonts`, `icon`, `supabase`\n- Runtime Modules: `@nuxt/eslint@1.4.1`, `reka-ui/nuxt@2.4.0`, `@nuxt/ui@3.3.0`, `@nuxtjs/supabase@1.5.2`, `@vueuse/nuxt@13.6.0`\n- Build Modules: `-`\n\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.3.0\n\n### Reproduction\n\nhttps://codesandbox.io/p/devbox/suspicious-lumiere-6jxxjc\n\n### Description\n\nWhen displaying the `UInputMenu`, with no items in the array (fetched later) but with a default value, the placeholder is shown instead of showing the string.\n\n### Additional context\n\nFaulty commit: 488707e\n\n#4528 \n\n### Logs\n\n```shell-script\n\n```",[3217,3218],{"name":3140,"color":3141},{"name":3143,"color":3144},4635,"`UInputMenu` does not display default model value (placeholder shown instead)","2025-08-14T09:04:53Z","https://github.com/nuxt/ui/issues/4635",0.64601696,{"description":3225,"labels":3226,"number":3232,"owner":3149,"repository":3150,"state":3198,"title":3233,"updated_at":3234,"url":3235,"score":3236},"### Environment\n\nNuxt UI pro v 3.1.0\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.1.0\n\n### Reproduction\n\nhttps://ui.nuxt.com/components/input-menu#control-search-term\n\n### Description\n\nHello, \n\nI am reopening an issue based on https://github.com/nuxt/ui/issues/3782\n\nI still have an issue on the InputMenu that filters with the default value.\n\nAs a reproduction : we can see the same behavior I am facing in the documentation : https://ui.nuxt.com/components/input-menu#control-search-term . \n\n1) => The first click on InputMenu shows only the seacherd term (here Backlog)\n2) => If I close the popover and reopen it a second time, it shows the entire list.\n\nI tried the :reset-search-term-on-select=\"false\" , it allows to display the entire list at 1st click but it leads to not showing the default selected value (the placeholder is displayed).\n\nActually, I am looking to display the entire list at first click, even if a value is already selected.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3227,3228,3229],{"name":3140,"color":3141},{"name":3143,"color":3144},{"name":3230,"color":3231},"reka-ui","56d799",3993,"InputMenu Clear Search on Select at first click","2025-07-16T10:57:06Z","https://github.com/nuxt/ui/issues/3993",0.6489394,{"description":3238,"labels":3239,"number":3249,"owner":3149,"repository":3150,"state":3198,"title":3250,"updated_at":3251,"url":3252,"score":3253},"### 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```",[3240,3241,3244,3245,3246],{"name":3140,"color":3141},{"name":3242,"color":3243},"needs reproduction","CB47CF",{"name":3143,"color":3144},{"name":3146,"color":3147},{"name":3247,"color":3248},"closed-by-bot","ededed",4103,"InputMenu Event onChange","2025-05-17T02:08:14Z","https://github.com/nuxt/ui/issues/4103",0.65435934,{"description":3255,"labels":3256,"number":3260,"owner":3149,"repository":3150,"state":3198,"title":3261,"updated_at":3262,"url":3263,"score":3264},"### Environment\n\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: bun@1.2.4\n- Builder: -\n- User Config: compatibilityDate, devtools, runtimeConfig, nitro, routeRules, modules, ui, supabase, site, feed, sitemap, robots, schemaOrg, image, hub\n- Runtime Modules: @nuxt/ui@3.0.1, @nuxtjs/supabase@1.5.0, @vueuse/nuxt@13.0.0, @nuxt/image@1.10.0, @nuxthub/core@0.8.18, @nuxtjs/sitemap@7.2.9, nuxt-module-feed@1.1.4, @nuxtjs/robots@5.2.8, nuxt-schema-org@5.0.4, nuxt-link-checker@4.3.0\n- Build Modules: -\n------------------------------\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.0.1\n\n### Reproduction\n\nhttps://codesandbox.io/p/devbox/adoring-gates-fd8q9s\n\n### Description\n\n## Expected behaviour\nValidation should trigger when a user adds or removes items from an input menu that has the `multiple` prop\n\n## Actual behaviour\nValidation seems to trigger when the input menu is opened or closed, but not when items are removed\n\n## Reproduction\n1. Use the codesandbox provided\n2. Add all 4 items to the input\n3. Validation should trigger saying 3 max\n4. Remove an item\n5. **Validation error persists, when it should be gone**\n6. Remove all the items\n7. Add a single item\n8. Remove them item\n9. **Validation error should appear stating 1 item min, but it doesn't**\n\n### Additional context\n\n## Screen capture\n\nhttps://github.com/user-attachments/assets/fccda9b1-2837-4b7d-85ad-5d63480582a1\n\n### Logs\n\n```shell-script\n\n```",[3257,3258,3259],{"name":3140,"color":3141},{"name":3143,"color":3144},{"name":3146,"color":3147},3726,"Form validation with InputMenu doesn't trigger when expected","2025-04-08T19:48:00Z","https://github.com/nuxt/ui/issues/3726",0.65564775,["Reactive",3266],{},["Set"],["ShallowReactive",3269],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fP6AssClxv24CwsywFwcH9m8FmYpsIAcCVMFoQHGe9yc":-1},"/nuxt/ui/4240"]