\n\n### Logs\n\n```shell-script\n\n```",[3018,3021,3024],{"name":3019,"color":3020},"bug","d73a4a",{"name":3022,"color":3023},"v3","49DCB8",{"name":3025,"color":3026},"triage","ffffff",4449,"nuxt","ui","open","Interfering Dropdown in `UNavigationMenu` component when using sections","2025-07-08T21:08:13Z","https://github.com/nuxt/ui/issues/4449",0.66294676,{"description":3036,"labels":3037,"number":3041,"owner":3028,"repository":3029,"state":3030,"title":3042,"updated_at":3043,"url":3044,"score":3045},"### Version\n\nLatest commit https://pkg.pr.new/@nuxt/ui@62ab016\n\n### Description\n\nWhen fetching items using [ignore-filter prop ](https://ui.nuxt.com/components/select-menu#with-ignore-filter) `\u003CUSelectMenu>` does not remember the current selection.\n\nCurrently it works only if the selected item stays in the items array which is barely the case if dealing with more than 10 items:\n\nhttps://github.com/user-attachments/assets/f5c6b264-52a5-4d8b-b015-242e36d91fdb\n\nThis happens in two cases:\n\n1. When selecting an item the searchTerm gets resetted, the items-array changes and the selected item is no more in it -> Select menu label becomes empty\n2. When an item is selected, but searching for other items that dont include seleced item -> Select menu label becomes empty\n\n### Reproduction\n\nAlso reproducable in the docs:\nhttps://ui.nuxt.com/components/select-menu#with-ignore-filter\n\nhttps://github.com/user-attachments/assets/ec3065bb-7cc2-4976-9dde-da99dd2311b6\n\nHere case 1 never happens because the jsonplaceholder-api only has just 5 user-items so the selected user is always in the default empty search result. BUT case 2 happens: Select a user, open select again, type in any other name that doesnt include first user -> Select menu label becomes empty (weirdly tho, the avatar stays)",[3038,3039,3040],{"name":3019,"color":3020},{"name":3022,"color":3023},{"name":3025,"color":3026},4582,"SelectMenu with fetched items (ignore-filter) doesnt remember current selection","2025-07-23T17:27:36Z","https://github.com/nuxt/ui/issues/4582",0.6646877,{"description":3047,"labels":3048,"number":3052,"owner":3028,"repository":3029,"state":3030,"title":3053,"updated_at":3054,"url":3055,"score":3056},"### Environment\n\n- Operating System: Darwin\n- Node Version: v23.11.0\n- Nuxt Version: 3.17.3\n- CLI Version: 3.25.1\n- Nitro Version: 2.11.12\n- Package Manager: npm@10.9.2\n- Builder: -\n- User Config: devtools, typescript, css, compatibilityDate, devServer, vite, runtimeConfig, app, ui, scripts, modules, sentry, sourcemap\n- Runtime Modules: @nuxt/ui@3.1.2, @pinia/nuxt@0.11.0, pinia-plugin-persistedstate/nuxt@4.3.0, @sentry/nuxt/module@9.19.0, @nuxt/scripts@0.11.7, @nuxt/eslint@1.4.0\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.1.2\n\n### Reproduction\n\nhttps://codesandbox.io/p/devbox/r7ryl3\n\n### Description\n\nI recently upgrade to NuxtUI 3.1.2 (from 3.0.1) and It's impossible (or I don't know) how to deal with custom type for `InputMenu`, I got some types issues on `label-key`, `v-model`, `items`, `slots` as you can see in my reproduction.\n\n### Additional context\n\n\n\n### Logs\n\n```shell-script\n\n```",[3049,3050,3051],{"name":3019,"color":3020},{"name":3022,"color":3023},{"name":3025,"color":3026},4182,"Custom type with InputMenu","2025-05-19T12:22:28Z","https://github.com/nuxt/ui/issues/4182",0.6724388,{"description":3058,"labels":3059,"number":3065,"owner":3028,"repository":3029,"state":3066,"title":3067,"updated_at":3068,"url":3069,"score":3070},"### Environment\n\n- Operating System: Darwin\n- Node Version: v22.14.0\n- Nuxt Version: 3.17.4\n- CLI Version: 3.25.1\n- Nitro Version: 2.11.12\n- Package Manager: pnpm@10.11.0\n- Builder: -\n- User Config: modules, devtools, css, ui, runtimeConfig, compatibilityDate, dayjs, eslint, image, sanity, supabase\n- Runtime Modules: @nuxt/eslint@1.4.1, @nuxt/ui@3.1.3, @nuxt/image@1.10.0, @nuxtjs/sanity@1.13.3, @nuxtjs/supabase@1.5.1, motion-v/nuxt@0.11.3, dayjs-nuxt@2.1.11, @pinia/nuxt@0.10.1\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.17.4\n\n### Reproduction\n\nHappens also in the Nuxt UI documentation: https://ui.nuxt.com/components/input-menu#items\n\n\n\n### Description\n\nI would expect that all list items appear on the first opening and not on the second one like in following video:\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3060,3061,3064],{"name":3019,"color":3020},{"name":3062,"color":3063},"duplicate","cfd3d7",{"name":3022,"color":3023},4240,"closed","InputMenu shows only seleceted value in the list on first opening","2025-05-28T08:08:48Z","https://github.com/nuxt/ui/issues/4240",0.6065202,{"description":3072,"labels":3073,"number":3079,"owner":3028,"repository":3029,"state":3066,"title":3080,"updated_at":3081,"url":3082,"score":3083},"### 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```",[3074,3075,3076],{"name":3019,"color":3020},{"name":3022,"color":3023},{"name":3077,"color":3078},"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.6483533,{"description":3085,"labels":3086,"number":3096,"owner":3028,"repository":3029,"state":3066,"title":3097,"updated_at":3098,"url":3099,"score":3100},"### 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```",[3087,3088,3091,3092,3093],{"name":3019,"color":3020},{"name":3089,"color":3090},"needs reproduction","CB47CF",{"name":3022,"color":3023},{"name":3025,"color":3026},{"name":3094,"color":3095},"closed-by-bot","ededed",4103,"InputMenu Event onChange","2025-05-17T02:08:14Z","https://github.com/nuxt/ui/issues/4103",0.64894545,{"description":3102,"labels":3103,"number":3107,"owner":3028,"repository":3029,"state":3066,"title":3108,"updated_at":3109,"url":3110,"score":3111},"### Environment\n\nNuxt: 3.15.0\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\n3.0.0-alpha.10\n\n### Reproduction\n\nhttps://codesandbox.io/p/sandbox/lucid-shape-9kk73c\n\n### Description\n\n\nDropdownMenu actions will not work after Udrawer closed.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3104,3105,3106],{"name":3019,"color":3020},{"name":3022,"color":3023},{"name":3025,"color":3026},3067,"UDrawer UDropdownMenu actions conflict","2025-05-23T13:35:59Z","https://github.com/nuxt/ui/issues/3067",0.6576077,{"description":3113,"labels":3114,"number":3118,"owner":3028,"repository":3029,"state":3066,"title":3119,"updated_at":3120,"url":3121,"score":3122},"### Environment\n\nnot needed\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.1.1\n\n### Reproduction\n\ncheck current docs: https://ui.nuxt.com/components/navigation-menu#content-orientation\n\n### Description\n\n\n\nThe dropdown is at wrong position... also the \"arrow\" prop doesnt work\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3115,3116,3117],{"name":3019,"color":3020},{"name":3022,"color":3023},{"name":3025,"color":3026},4073,"UNavigationMenu: Dropdown broken","2025-05-13T12:02:03Z","https://github.com/nuxt/ui/issues/4073",0.6594492,{"description":3124,"labels":3125,"number":3131,"owner":3028,"repository":3029,"state":3066,"title":3132,"updated_at":3133,"url":3134,"score":3135},"### 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_",[3126,3127,3128,3129],{"name":3019,"color":3020},{"name":3025,"color":3026},{"name":3094,"color":3095},{"name":3130,"color":3095},"stale",1987,"[Bug] Select/SelectMenu popper open when clicking #trailing","2025-06-19T02:12:14Z","https://github.com/nuxt/ui/issues/1987",0.6630273,{"description":3137,"labels":3138,"number":3142,"owner":3028,"repository":3029,"state":3066,"title":3143,"updated_at":3144,"url":3145,"score":3146},"### Environment\n\n- Operating System: `Darwin`\n- Node Version: `v22.13.0`\n- Nuxt Version: `3.16.2`\n- CLI Version: `3.24.1`\n- Nitro Version: `2.11.9`\n- Package Manager: `pnpm@10.8.1`\n- Builder: `-`\n- User Config: `modules`, `devtools`, `css`, `site`, `future`, `compatibilityDate`, `echarts`, `eslint`, `fonts`, `icon`, `sitemap`\n- Runtime Modules: `@nuxtjs/sitemap@7.2.10`, `@nuxt/content@3.4.0`, `@nuxt/eslint@1.3.0`, `@nuxt/ui-pro@3.0.2`, `@vueuse/nuxt@13.1.0`, `nuxt-echarts@0.3.0`\n- Build Modules: `-`\n\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.0.2\n\n### Reproduction\n\nhttps://codesandbox.io/p/devbox/peaceful-elbakyan-3ddsxd\n\n### Description\n\nMy understanding is that the onSelect event of SelectMenu should be consistent with the DropdownMenu component, but in reality, it is not.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3139,3140,3141],{"name":3019,"color":3020},{"name":3022,"color":3023},{"name":3025,"color":3026},3978,"The onSelect event of the SelectMenu component was not triggered","2025-05-05T15:20:55Z","https://github.com/nuxt/ui/issues/3978",0.66667765,["Reactive",3148],{},["Set"],["ShallowReactive",3151],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fkeZ00VBjTiTHMeGCGRxljfQbSe5VctJVbmx0pVxklpQ":-1},"/nuxt/ui/4100"]