\n\nIt can be worked around using `item-label` slot, but it would be nice if developer can use `items` props only to implement it for simpler way.\n\nBelow, I have tried to create it using Reka UI `combobox` component, the component used by SelectMenu.\n\n\u003Cimg width=\"329\" height=\"460\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/e5cda771-3f8e-4369-bb3b-d5159f84d425\" />\n\n### Additional context\n\n_No response_",[3201,3202,3203],{"name":3172,"color":3173},{"name":3175,"color":3176},{"name":3178,"color":3179},4661,"SelectMenu: add description props to show text below title","2025-08-06T02:19:32Z","https://github.com/nuxt/ui/issues/4661",0.73789376,{"description":3210,"labels":3211,"number":3214,"owner":3181,"repository":3182,"state":3183,"title":3215,"updated_at":3216,"url":3217,"score":3218},"### Package\n\nv4.x\n\n### Description\n\nWe need the ability to target nested parts of a component during automated tests.\n\nFor instance, let's say we have a SelectMenu component and we set data-testid='fruit-selector' to select it in an end-to-end test. We then need to target the input element inside it. Currently, we have to use classes or element tags in a nested selector, which can be cumbersome.\n\nMy idea is to have a system for data-* attributes that is similar to the class configuration we use for each slot.\n\nThis would allow us to target the fruit selector's input with:\n[data-testid='fruitselector'] > [data-testid=\"select-menu-input-search\"]\n\nAnd if we had another select menu, we could target its input with:\n[data-testid='colorselector'] > [data-testid=\"select-menu-input-search\"]\n\n\nwhat do you think about it? Is it feasable?\n\n### Additional context\n\n_No response_",[3212,3213],{"name":3172,"color":3173},{"name":3178,"color":3179},5137,"data-attributes on nested slot","2025-10-03T14:54:31Z","https://github.com/nuxt/ui/issues/5137",0.7411529,{"description":3220,"labels":3221,"number":3225,"owner":3181,"repository":3182,"state":3183,"title":3226,"updated_at":3227,"url":3228,"score":3229},"### Description\n\nWhen using `multiple` with `USelectMenu` selected items can be deselected again. But when not having `multipe` option this is not the case. The select goes from undefined to a value and then can never become undefined again (without an external button).\n\nI would propose to add a new prop that allows values to be deselected, so the model becomes undefined again.\n\n### Additional context\n\n_No response_",[3222,3223,3224],{"name":3172,"color":3173},{"name":3175,"color":3176},{"name":3178,"color":3179},4647,"`USelectMenu`: Allow deselection of items","2025-08-02T13:00:23Z","https://github.com/nuxt/ui/issues/4647",0.7475459,{"description":3231,"labels":3232,"number":3235,"owner":3181,"repository":3182,"state":3183,"title":3236,"updated_at":3237,"url":3238,"score":3239},"### Package\n\nv4.x\n\n### Description\n\nI've been using successfully a very similar component to handle `ButtonGroup` messing with nested controls:\n\n```vue\n\u003Ctemplate>\n \u003CUFieldGroup>\n \u003CUInput\n v-model=\"text\"\n />\n\n \u003CUDrawer>\n \u003CUChip\n :show=\"anyFilter\"\n >\n \u003CUButton\n icon=\"lucide:filter\"\n />\n \u003C/UChip>\n\n \u003Ctemplate #content>\n \u003CUClearFieldGroup>\n \u003CFilters />\n \u003C/UClearFieldGroup>\n \u003C/template>\n \u003C/UDrawer>\n \u003C/UFieldGroup>\n\u003C/template>\n```\n\nReference: #4242 \n\n### Additional context\n\n_No response_",[3233,3234],{"name":3172,"color":3173},{"name":3178,"color":3179},5045,"\u003CClearFieldGroup>","2025-09-23T13:26:53Z","https://github.com/nuxt/ui/issues/5045",0.7506703,{"description":3241,"labels":3242,"number":3247,"owner":3181,"repository":3182,"state":3183,"title":3248,"updated_at":3249,"url":3250,"score":3251},"### Environment\n\n- OS: Windows\n- Nuxt: v4.0.3\n- Node: v22.14.0\n\n### Version\n\nv4.0.3\n\n### Reproduction\n\nhttps://stackblitz.com/edit/nuxt-ui-gtu8vgxz?file=app.vue\n\n### Description\n\nThe USelectMenu component does not block form validation even when setting the required prop.\nI though this was a bug since the USelect component instead correctly blocks validation when setting the required prop.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3243,3246],{"name":3244,"color":3245},"bug","d73a4a",{"name":3178,"color":3179},4757,"USelectMenu required prop is not blocking form validation","2025-08-15T10:52:46Z","https://github.com/nuxt/ui/issues/4757",0.75243384,{"description":3253,"labels":3254,"number":3258,"owner":3181,"repository":3182,"state":3183,"title":3259,"updated_at":3260,"url":3261,"score":3262},"### Description\n\nI would like to use the InputNumber component, but I don't necessarily want the increment/decrement buttons to show up.\n\n### Additional context\n\n_No response_",[3255,3256,3257],{"name":3172,"color":3173},{"name":3175,"color":3176},{"name":3178,"color":3179},4718,"[InputNumber] add option to hide increment/decrement buttons","2025-08-12T08:05:11Z","https://github.com/nuxt/ui/issues/4718",0.7584972,{"description":3264,"labels":3265,"number":3273,"owner":3181,"repository":3182,"state":3274,"title":3275,"updated_at":3276,"url":3277,"score":3278},"### Description\n\nTo enhance user experience in some cases we can show selected values as Badges(chips) and it helps the user to see selected values. It can even deselect it without the need to open the list and find between long items. \r\n\r\neg: \r\n\r\n\r\n\r\n\r\nIt can be very helpful for developers and it's a handy feature.\r\n\r\nI implemented it and I will make PR for that soon :).\r\n\n\n### Additional context\n\n_No response_",[3266,3267,3268,3271],{"name":3172,"color":3173},{"name":3175,"color":3176},{"name":3269,"color":3270},"closed-by-bot","ededed",{"name":3272,"color":3270},"stale",1088,"closed","Badges as display value for SelectMenu component","2025-08-18T02:13:52Z","https://github.com/nuxt/ui/issues/1088",0.7316244,{"description":3280,"labels":3281,"number":3285,"owner":3181,"repository":3182,"state":3274,"title":3286,"updated_at":3287,"url":3288,"score":3289},"### Description\n\nNeed to have the ability to provide a callback function to onRemoveTag when selecting multiple items to be able to customize its behavior.\n\n### Additional context\n\nIn my use case for example I have an InputMenu with Multiple selections the items list contains values that fall under multiple categories for example A, B, and C with the ability to search for any of them in the same InputMenu, so the list of items looks something like this:\n- A: A1\n- A: A2\n- B: B5\n- C: C7\nthe state is then stored in a pinia store based on the category onSelect, e.g. `if (key == \"A\") store.listA.push(item.value)` when I click on the remove tag the v-model value is updated, but I have no idea which category was it from, meaning I will have to check all the items to know which state to update since they are actually separate.",[3282,3283,3284],{"name":3172,"color":3173},{"name":3175,"color":3176},{"name":3178,"color":3179},4463,"[InputMenu] ability to control behavior of onRemoveTag","2025-07-16T20:28:46Z","https://github.com/nuxt/ui/issues/4463",0.7409301,["Reactive",3291],{},["Set"],["ShallowReactive",3294],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fJJW6X7JU4As7L5_fTFa7bK94zBrJg0aM7GBm2vV5XB8":-1},"/nuxt/ui/5088"]