\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```",[3049,3050,3051],{"name":3019,"color":3020},{"name":3022,"color":3023},{"name":3025,"color":3026},4530,"[UInputTags, UInputMenu] Theming behaviour issues","2025-07-15T17:50:02Z","https://github.com/nuxt/ui/issues/4530",0.6877606,{"description":3058,"labels":3059,"number":3063,"owner":3028,"repository":3028,"state":3030,"title":3064,"updated_at":3065,"url":3066,"score":3067},"### Environment\n\n------------------------------\r\n- Operating System: Linux\r\n- Node Version: v20.11.0\r\n- Nuxt Version: 3.11.2\r\n- CLI Version: 3.11.1\r\n- Nitro Version: 2.9.6\r\n- Package Manager: pnpm@9.1.4\r\n- Builder: -\r\n- User Config: modules, experimental, ssr, css, colorMode, nitro, app, pwa, devtools, eslintConfig, i18n, vite, runtimeConfig\r\n- Runtime Modules: @vueuse/nuxt@10.10.0, @unocss/nuxt@0.58.9, @pinia/nuxt@0.5.1, @pinia-plugin-persistedstate/nuxt@1.2.0, @nuxtjs/color-mode@3.4.1, @vite-pwa/nuxt@0.4.0, @bg-dev/nuxt-naiveui@1.10.1, @nuxtjs/i18n@8.3.1, unplugin-icons/nuxt, nuxt-module-eslint-config@0.1.1\r\n- Build Modules: -\r\n------------------------------\r\n\n\n### Reproduction\n\nNuxt Config:\r\n```ts\r\nexport default defineNuxtConfig({\r\n // ...\r\n runtimeConfig: {\r\n public: {\r\n test: 'prerendered \"test value\" (default)',\r\n onlyRuntime: 'prerendered \"only runtime value\" (default)'\r\n },\r\n },\r\n nitro: {\r\n esbuild: {\r\n options: {\r\n target: 'esnext',\r\n },\r\n },\r\n prerender: {\r\n crawlLinks: false,\r\n routes: ['/'],\r\n },\r\n },\r\n // ...\r\n})\r\n```\r\n\r\n`pages/index.vue`\r\n\r\n```vue\r\n\u003Ctemplate>\r\n \u003Cdiv>\r\n \u003Ch1>This Page is prerendered\u003C/h1>\r\n {{config.public.test}} \u003Cbr>\r\n \u003CNuxtLink to=\"/test\">SSR page\u003C/NuxtLink>\r\n \u003C/div>\r\n\u003C/template>\r\n\r\n\u003Cscript setup lang=\"ts\">\r\nconst config = useRuntimeConfig()\r\n\u003C/script>\r\n```\r\n\r\n`pages/test.vue`\r\n\r\n```vue\r\n\u003Ctemplate>\r\n \u003Cdiv>\r\n \u003Ch1>This Page is not prerendered\u003C/h1>\r\n {{config.public.test}}\u003Cbr>\r\n {{config.public.onlyRuntime}}\u003Cbr>\r\n \u003CNuxtLink to=\"/\">prerendered Page\u003C/NuxtLink>\r\n \u003C/div>\r\n\u003C/template>\r\n\r\n\u003Cscript setup lang=\"ts\">\r\nconst config = useRuntimeConfig()\r\n\u003C/script>\r\n```\r\n\r\nenv for `node .output/server/index.mjs`\r\n\r\n```yaml\r\n environment:\r\n - NUXT_PUBLIC_TEST=runtime \"test value\"\r\n - NUXT_PUBLIC_ONLY_RUNTIME=runtime \"only runtime value\"\r\n```\r\n\r\nlink to deployed version: https://app.runtime-config-example.v2.singular-it-test.de/\n\n### Describe the bug\n\nSteps:\r\n1. open https://app.runtime-config-example.v2.singular-it-test.de/\r\n2. see varaibles\r\n3. navigate to SSR page\r\n4. variables are still from builttime\r\n5. refresh page\r\n6. variables are now from runtime\r\n7. navigate back to prerendered\r\n8. variables are still runtime\n\n### Additional context\n\ni think it will be intended that way, but i find the behavior of the runtimeConfig sometimes a bit inconsistent, especially if you prerender parts of the app and others not. (and thus also with regard to the caching of pwa). Depending on the entry point in the app (i.e. whether generated or dynamic), this can lead to different configs, which then persist between the dynamic and static pages. \r\n\r\ni don't expect prerendered parts of the app to pick up the runtime config, but i would assume that when i switch from a static to a non-static page, the runtime variables also play a role. Otherwise, as soon as prerender is active, everything should be set at build time (so that there can no longer be a runtime config) and everything is/needs to be set in the build step to avoid differences depending on the entry point.\r\n\r\nI know that it is not necessarily common to have a different config for generation than for runtime, but especially in my case it is not necessary to set all variables in the build (prerender). and generally the runtime config is also there to set the variables when running the app.\n\n### Logs\n\n_No response_",[3060],{"name":3061,"color":3062},"pending triage","E99695",28847,"strange runtimeConfig behaviour when prerendering parts of the app","2024-09-06T11:27:57Z","https://github.com/nuxt/nuxt/issues/28847",0.6948274,{"description":3069,"labels":3070,"number":3076,"owner":3028,"repository":3029,"state":3077,"title":3078,"updated_at":3079,"url":3080,"score":3081},"### 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```",[3071,3072,3075],{"name":3019,"color":3020},{"name":3073,"color":3074},"duplicate","cfd3d7",{"name":3022,"color":3023},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":3083,"labels":3084,"number":3090,"owner":3028,"repository":3029,"state":3077,"title":3091,"updated_at":3092,"url":3093,"score":3094},"### 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```",[3085,3086,3087],{"name":3019,"color":3020},{"name":3022,"color":3023},{"name":3088,"color":3089},"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":3096,"labels":3097,"number":3107,"owner":3028,"repository":3029,"state":3077,"title":3108,"updated_at":3109,"url":3110,"score":3111},"### 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```",[3098,3099,3102,3103,3104],{"name":3019,"color":3020},{"name":3100,"color":3101},"needs reproduction","CB47CF",{"name":3022,"color":3023},{"name":3025,"color":3026},{"name":3105,"color":3106},"closed-by-bot","ededed",4103,"InputMenu Event onChange","2025-05-17T02:08:14Z","https://github.com/nuxt/ui/issues/4103",0.65435934,{"description":3113,"labels":3114,"number":3118,"owner":3028,"repository":3029,"state":3077,"title":3119,"updated_at":3120,"url":3121,"score":3122},"### 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```",[3115,3116,3117],{"name":3019,"color":3020},{"name":3022,"color":3023},{"name":3025,"color":3026},3726,"Form validation with InputMenu doesn't trigger when expected","2025-04-08T19:48:00Z","https://github.com/nuxt/ui/issues/3726",0.65564775,{"description":3124,"labels":3125,"number":3127,"owner":3028,"repository":3028,"state":3077,"title":3128,"updated_at":3129,"url":3130,"score":3131},"### Environment\n\n------------------------------\r\n- Operating System: Linux\r\n- Node Version: v20.14.0\r\n- Nuxt Version: 3.12.4\r\n- CLI Version: 3.12.0\r\n- Nitro Version: 2.9.7\r\n- Package Manager: pnpm@9.7.1\r\n- Builder: -\r\n- User Config: runtimeConfig, extends, modules, ui, colorMode, routeRules, devtools, typescript, future, eslint, nitro, i18n, compatibilityDate\r\n- Runtime Modules: @nuxt/eslint@0.5.0, @nuxt/fonts@0.7.1, @nuxt/ui@2.18.4, @vueuse/nuxt@10.11.0, @nuxtjs/i18n@8.5.0\r\n- Build Modules: -\r\n------------------------------\r\n\n\n### Reproduction\n\nhttps://stackblitz.com/edit/nuxt-ui-u6tm1b?file=app.vue\n\n### Describe the bug\n\nWhen using a `v-model` prop with some initial object values (such as fetched already selected data from backend), the `\u003CUSelectMenu>` component doesn't show these as selected and seems to ignore them completely.\r\n\r\nEven when selecting the same objects again, it just seems to add them to the array and disregard anything, that was there previously.\n\n### Additional context\n\nThe behaviour changes when setting the `by` prop. In my case, I set it to `id`, after which I can see the object as selected, **but only** in the dropdown.\r\nThe button itself still shows `0 selected`.\n\n### Logs\n\n_No response_",[3126],{"name":3061,"color":3062},28733,"SelectMenu initial object values","2024-08-28T03:27:34Z","https://github.com/nuxt/nuxt/issues/28733",0.65784067,{"description":3133,"labels":3134,"number":3138,"owner":3028,"repository":3029,"state":3077,"title":3139,"updated_at":3140,"url":3141,"score":3142},"### Environment\n\n```\n- Operating System: Darwin\n- Node Version: v22.14.0\n- Nuxt Version: 3.16.2\n- CLI Version: 3.24.1\n- Nitro Version: 2.11.9\n- Package Manager: bun@1.2.9\n- Builder: -\n- User Config: ssr, imports, devtools, experimental, future, compatibilityDate, alias, runtimeConfig, devServer, app, css, modules, build, hooks, dayjs, ui, typescript\n- Runtime Modules: @nuxt/eslint@1.3.0, @vueuse/nuxt@13.1.0, @nuxt/test-utils/module@3.17.2, dayjs-nuxt@2.1.11, nuxt-svgo@4.0.17, @nuxt/ui-pro@3.1.0, @pinia/nuxt@0.11.0, @pinia/colada-nuxt@0.1.1, @nuxt/image@1.10.0\n- Build Modules: -\n```\n\n\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\n3.1.0\n\n### Reproduction\n\nhttps://codesandbox.io/p/devbox/empty-fast-5xtcmy?workspaceId=ws_SD2P6X4ufyWkm2P3aqoQA6\n\n### Description\n\nbetween version 3.0.2 and 3.1.0 the content container for the menu items is no longer filling the width.\n\n### Additional context\n\n__no response__\n\n### Logs\n\n```shell-script\n\n```",[3135,3136,3137],{"name":3019,"color":3020},{"name":3022,"color":3023},{"name":3025,"color":3026},3987,"[NavigationMenu] Regression - Update","2025-05-02T09:52:45Z","https://github.com/nuxt/ui/issues/3987",0.66692424,["Reactive",3144],{},["Set"],["ShallowReactive",3147],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fP6AssClxv24CwsywFwcH9m8FmYpsIAcCVMFoQHGe9yc":-1},"/nuxt/ui/4240"]