\n```\n\n\n### Description\n\nWhen using `UInputMenu`, each item can be assigned a custom class. However, after filtering, the class assignment seems to mismatch. For example, the \"Green\" item may be displayed in red color.\n\n### Additional context\n\n- Initial state (before filtering): \n\u003Cimg width=\"328\" height=\"243\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/f556d5b4-554e-4328-98f1-e3bb037504bf\" />\n\n- After filtering with \"r\": \n\u003Cimg width=\"338\" height=\"206\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/bbed6c9b-2eae-4c55-9d68-2991f64c26ca\" />\n\nIn the filtered state, the \"Green\" item is incorrectly displayed in red.\n\n### Logs\n\n```shell-script\n\n```",[3157,3158,3159],{"name":3138,"color":3139},{"name":3141,"color":3142},{"name":3144,"color":3145},4752,"UInputMenu item class mismatch after filtering","2025-08-15T01:57:20Z","https://github.com/nuxt/ui/issues/4752",0.7064636,{"description":3166,"labels":3167,"number":3171,"owner":3147,"repository":3148,"state":3149,"title":3172,"updated_at":3173,"url":3174,"score":3175},"### Environment\n\n```\n- Node Version: v20.12.0\n- Nuxt Version: 3.17.3\n- Runtime Modules: @nuxt/ui@3.3.3\n- Browser: Chromium 136 (windows)\n```\n\n#### Version\n\nv3.3.3\n\n### Reproduction\n\nhttps://codesandbox.io/p/devbox/mutable-frog-xc2v8p\n\n### Description\n\nHello Nuxt Ui team!\n\nI noticed two issues with `USelect` & `USelectMenu`:\n\n1. **Input autofocus issue:** \n When typing in the input, opening the select causes the input to lose focus. Setting `:autofocus=\"false\"` has no effect, the select is still focused when opened.\n\n2. **Body lock issue:** \n Setting `:content=\"{ bodyLock: false }\"` does not prevent the body from being locked. The CSS property `pointer-events: default;` is still applied on the body.\n\nIn the case of an autocomplete, this prevents continuing to type in the input while still displaying suggested results.\n\nThanks for your help!\n",[3168,3169,3170],{"name":3138,"color":3139},{"name":3141,"color":3142},{"name":3144,"color":3145},4956,"`USelect` & `USelectMenu` setting :autofocus to false or :content `bodyLock` to false have no effect","2025-09-12T12:07:19Z","https://github.com/nuxt/ui/issues/4956",0.7074609,{"description":3177,"labels":3178,"number":3182,"owner":3147,"repository":3148,"state":3149,"title":3183,"updated_at":3184,"url":3185,"score":3186},"### Environment\n\n- Operating System: Windows_NT\n- Node Version: v22.14.0\n- Nuxt Version: 3.17.1\n- CLI Version: 3.25.0\n- Nitro Version: 2.11.11\n- Package Manager: npm@10.9.2\n- Builder: -\n- User Config: compatibilityDate, future, devtools, app, runtimeConfig, hooks, components, modules, eslint, ui, css, telemetry\n- Runtime Modules: @nuxt/eslint@1.3.0, @nuxt/ui@3.1.1, @pinia/nuxt@0.11.0\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.1.1\n\n### Reproduction\n\n1. Add a `USelect` component to a page with any example from the official doc: https://ui.nuxt.com/components/select\n2. Start dev mode: `npm run dev`\n3. Opens the page and try interact with the select element with **Vue dev tool opened**\n\n### Description\n\nThe `USelect` component responds really slow upon user clicks (20+ seconds to open/close for a select with 100+ items), this also applies to some other components such as `UDropdownMenu` and `USelectMenu`.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3179,3180,3181],{"name":3138,"color":3139},{"name":3141,"color":3142},{"name":3144,"color":3145},4142,"USelect and USelectMenu responds really slow when Vue devtool is opened","2025-05-13T13:28:11Z","https://github.com/nuxt/ui/issues/4142",0.7111772,{"description":3188,"labels":3189,"number":3195,"owner":3147,"repository":3148,"state":3196,"title":3197,"updated_at":3198,"url":3199,"score":3200},"### 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```",[3190,3191,3194],{"name":3138,"color":3139},{"name":3192,"color":3193},"duplicate","cfd3d7",{"name":3141,"color":3142},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.6694146,{"description":3202,"labels":3203,"number":3209,"owner":3147,"repository":3148,"state":3196,"title":3210,"updated_at":3211,"url":3212,"score":3213},"### 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```",[3204,3205,3206],{"name":3138,"color":3139},{"name":3141,"color":3142},{"name":3207,"color":3208},"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.67071193,{"description":3215,"labels":3216,"number":3220,"owner":3147,"repository":3147,"state":3196,"title":3221,"updated_at":3222,"url":3223,"score":3224},"### 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_",[3217],{"name":3218,"color":3219},"pending triage","E99695",28733,"SelectMenu initial object values","2024-08-28T03:27:34Z","https://github.com/nuxt/nuxt/issues/28733",0.67226744,{"description":3226,"labels":3227,"number":3230,"owner":3147,"repository":3148,"state":3196,"title":3231,"updated_at":3232,"url":3233,"score":3234},"### Environment\n\n------------------------------\n- Operating System: Darwin\n- Node Version: v20.19.2\n- Nuxt Version: -\n- CLI Version: 3.28.0\n- Nitro Version: -\n- Package Manager: npm@10.8.2\n- Builder: -\n- User Config: -\n- Runtime Modules: -\n- Build Modules: -\n------------------------------\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Package\n\nv3.x\n\n### Version\n\nv3.3.3\n\n### Reproduction\n\nhttps://stackblitz.com/edit/github-mj4wqh54?file=app%2Fpages%2Findex.vue\n\n### Description\n\nWhen using `InputMenu`, `Select` or `SelectMenu`, if the `modelValue` is `null` (or another falsy value) and an option with this value exists, its `label` is not displayed.\n\n**Expected behavior**:\nIf an option with a `null` (or falsy) value is present in the `options`, its `label` should be displayed when selected.\n\n**Example**:\n\n```vue\n\u003CUSelect\n v-model=\"value\"\n :items=\"[\n { name: '- Tout -', slug: null },\n { name: 'Sport', slug: 'sport' },\n { name: 'Culture', slug: 'culture' },\n ]\"\n value-key=\"slug\"\n label-key=\"name\"\n />\n```\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3228,3229],{"name":3138,"color":3139},{"name":3141,"color":3142},4869,"InputMenu/Select/SelectMenu: show falsy label when model value is falsy","2025-09-08T12:42:34Z","https://github.com/nuxt/ui/issues/4869",0.6723035,{"description":3236,"labels":3237,"number":3245,"owner":3147,"repository":3148,"state":3196,"title":3246,"updated_at":3247,"url":3248,"score":3249},"### Environment\r\n\r\n- Operating System: Darwin\r\n- Node Version: v20.10.0\r\n- Nuxt Version: 3.12.2\r\n- CLI Version: 3.12.0\r\n- Nitro Version: 2.9.6\r\n- Package Manager: pnpm@9.6.0\r\n- Builder: -\r\n- User Config: devtools, vite, routeRules, app, css, imports, runtimeConfig, modules, auth, i18n, colorMode\r\n- Runtime Modules: @nuxtjs/i18n@8.0.0, @sidebase/nuxt-auth@0.6.4, @vueuse/nuxt@10.11.0\r\n- Build Modules: -\r\n\r\n### Version\r\n\r\n2.18.1\r\n\r\n### Reproduction\r\n\r\n[https://stackblitz.com/edit/nuxt-ui-ubowv1?file=app.vue](https://stackblitz.com/edit/nuxt-ui-ubowv1?file=app.vue)\r\n\r\n### Description\r\n\r\nI'm trying to clear the item selected in a selectmenu using the `#trailling` slot. But it doesn't matter, it opens the menu instead. I've tried applying the `.stop` modifier but it's the same thing.\r\n\r\nIs this a bug or am I doing something wrong?\r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n### Logs\r\n\r\n_No response_",[3238,3239,3240,3243],{"name":3138,"color":3139},{"name":3144,"color":3145},{"name":3241,"color":3242},"closed-by-bot","ededed",{"name":3244,"color":3242},"stale",1987,"[Bug] Select/SelectMenu popper open when clicking #trailing","2025-06-19T02:12:14Z","https://github.com/nuxt/ui/issues/1987",0.67849946,{"description":3251,"labels":3252,"number":3259,"owner":3147,"repository":3148,"state":3196,"title":3260,"updated_at":3261,"url":3262,"score":3263},"### Environment\n\n------------------------------\n- Operating System: Darwin\n- Node Version: v24.2.0\n- Nuxt Version: 4.0.1\n- CLI Version: 3.27.0\n- Nitro Version: 2.12.4\n- Package Manager: npm@11.3.0\n- Builder: -\n- User Config: compatibilityDate, devtools, extends, pinia, css, ui, modules, runtimeConfig, nitro\n- Runtime Modules: @nuxt/eslint@1.7.1, @nuxt/image@1.10.0, @nuxt/ui@3.3.0, @pinia/nuxt@0.11.2, pinia-plugin-persistedstate/nuxt@4.4.1\n- Build Modules: -\n------------------------------\n\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\n4.0.1\n\n### Reproduction\n\n```\n\u003Ctemplate>\n \u003Cdiv class=\"flow-root mb-3\">\n \u003Cul role=\"list\" class=\"-my-6 divide-y divide-gray-200\">\n \u003Cli v-for=\"product in basketStore.items\" :key=\"product.rid\" class=\"flex py-6\">\n \u003Cdiv class=\"hidden sm:block h-24 w-24 flex-shrink-0 overflow-hidden rounded-md border border-gray-200\">\n \u003CProductsProductImage />\n \u003C/div>\n\n \u003Cdiv class=\"ml-4 flex flex-1 flex-col\">\n \u003Cdiv>\n \u003Cdiv class=\"flex justify-between text-base font-medium text-gray-900 mb-2\">\n \u003CNuxtLink :to=\"'/product/' + product.id\">{{ product.name }}\u003C/NuxtLink>\n \u003Cp class=\"ml-4\">£{{ product.selectedQuantity?.price }}\u003C/p>\n \u003C/div>\n \u003C/div>\n\n \u003Cdiv class=\"flex flex-1 flex-col md:flex-row items-end justify-between text-sm text-black gap-4\">\n \u003Cdiv class=\"w-full flex flex-col md:flex-row flex-wrap gap-2 \">\n \u003CUSelectMenu v-if=\"hasMultipleSkus(product)\" class=\"max-w-56\" v-model=\"product.selectedSku\"\n :search-input=\"false\" :label-key=\"'name'\" :items=\"product.skus\"\n @update:modelValue=\"changeSku($event as Sku, product)\">\n \u003C/USelectMenu>\n \u003Cpre>{{ product.selectedQuantity }}\u003C/pre>\n \u003CUSelectMenu v-model=\"product.selectedQuantity\" :search-input=\"false\"\n :label-key=\"'quantity'\" class=\"max-w-56\" :items=\"updatePricesWithStock(product)\"\n @update:modelValue=\"changeQuantity($event as QuantityPrice, product)\">\n \u003Ctemplate #item=\"{ item }\">\u003Cspan>{{ item.quantity }}\u003C/span>\u003Cspan\n v-if=\"item.disabled\">Out of\n stock\u003C/span>\u003C/template>\n \u003C/USelectMenu>\n \u003C/div>\n \u003Cdiv class=\"flex\">\n \u003Cbutton type=\"button\" class=\"font-medium text-primary-500 hover:text-primary-600\"\n @click=\"basketStore.remove(product.rid)\">Remove\u003C/button>\n \u003C/div>\n\n \u003C/div>\n\n \u003C/div>\n \u003C/li>\n\n \u003C/ul>\n \u003C/div>\n\u003C/template>\n\u003Cscript setup lang=\"ts\">\nimport type { Product, Sku, QuantityPrice } from '../../types';\n\nfunction changeSku(sku: Sku, item: Product) {\n\n}\n\nfunction hasMultipleSkus(item: Product): boolean {\n\n}\n\n\nfunction changeQuantity(quantity: QuantityPrice, item: Product) {\n\n}\n\n// Helper function to map prices and add \"disabled\" property - see other \nconst updatePricesWithStock = (item: any) => {\n return item.selectedSku?.prices.map((price: QuantityPrice) => ({\n ...price,\n disabled: !item?.onDemand && price.quantity > item.selectedSku?.stock\n }));\n};\n\n\n\u003C/script>\n```\n\n### Description\n\n_(Not sure whether to include this issue in Nuxt or Nuxt UI)_\n\nI have a base component that uses a selectMenu with an array. In Nuxt 3.17.6 with compatibiltyVersion: 4 set, the SelectMenu works as expected. When upgrading to nuxt 4 the label key no longer works. I'll attach screenshots and the code is in the reproduction section.\n**Nuxt 3.17.6**\n\u003Cimg width=\"736\" height=\"216\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/04967fa3-d156-46e2-b74d-f060ec68fcc4\" />\n\n**Nuxt 4**\n\u003Cimg width=\"751\" height=\"220\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/8ccf4caf-12f1-46d0-beda-9ebea3b1eee3\" />\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3253,3254,3257,3258],{"name":3138,"color":3139},{"name":3255,"color":3256},"needs reproduction","CB47CF",{"name":3141,"color":3142},{"name":3144,"color":3145},4627,"SelectMenu | Label Key not working correctly with Nuxt 4?","2025-07-30T09:17:46Z","https://github.com/nuxt/ui/issues/4627",0.68139446,["Reactive",3265],{},["Set"],["ShallowReactive",3268],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$f1fEtJoVykl3LIHV58VD-y2sdd3G7Ev_mofVspC-M_jk":-1},"/nuxt/ui/4582"]