\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_",[3167,3168,3169],{"name":3138,"color":3139},{"name":3141,"color":3142},{"name":3144,"color":3145},4661,"SelectMenu: add description props to show text below title","2025-08-06T02:19:32Z","https://github.com/nuxt/ui/issues/4661",0.7575884,{"description":3176,"labels":3177,"number":3181,"owner":3147,"repository":3148,"state":3149,"title":3182,"updated_at":3183,"url":3184,"score":3185},"### Description\n\nThis feature request proposes that the InputNumber component be enhanced with leading and trailing slot support. \n\nCurrently, components such as **Input**, **InputMenu**, **Select**, and **SelectMenu** already offer these slots for inserting custom content. For consistency across the UI library and to provide developers with a uniform customization experience, it is imperative that InputNumber is updated to include both leading and trailing slots. \n\n### Additional context\n\n_No response_",[3178,3179,3180],{"name":3138,"color":3139},{"name":3141,"color":3142},{"name":3144,"color":3145},4201,"[InputNumber] Add support for leading & trailing slots","2025-05-21T13:07:28Z","https://github.com/nuxt/ui/issues/4201",0.76509756,{"description":3187,"labels":3188,"number":3191,"owner":3147,"repository":3148,"state":3149,"title":3192,"updated_at":3193,"url":3194,"score":3195},"### Description\n\nDear Contributors,\n\nNuxtUI has been a great help in my app development. Thank you very much.\n\nI would like to request the addition of a new feature. I would appreciate your consideration.\n\n\nCommon search engines provide a search bar with a suggestion feature.\nSelecting a keyword from the provided suggestions is optional; if a user does not select a suggestion, the content they have entered takes precedence.\n\nHowever, the current InputMenu specifications automatically select the first item on the list if the user doesn't make a selection, overwriting the user's input with that value.\nIt would be useful if there were a feature that limited the overwriting of user input to only cases where the user explicitly selects an item from the list.\n\nThank you.\n\n### Additional context\n\n_No response_",[3189,3190],{"name":3138,"color":3139},{"name":3144,"color":3145},4717,"InputMenu want to selection to optional","2025-08-12T05:38:55Z","https://github.com/nuxt/ui/issues/4717",0.775472,{"description":3197,"labels":3198,"number":3201,"owner":3147,"repository":3148,"state":3202,"title":3203,"updated_at":3204,"url":3205,"score":3206},"### Description\n\nThis would be a new prop for `UInputTags` that would allow you to set a max length on the items being added. \n\n```\n\u003CInputTags v-model=\"items\" :max-item-length=\"25\" />\n\nconst items = ref([\n \"ok\",\n \"this one would not be ok because of how long it is\"\n])\n```\n\nThough, you could use something like Zod to do form validation, I think this could just apply a `maxlength` to the input itself to prevent typing more than the limit.\n\n### Additional context\n\n_No response_",[3199,3200],{"name":3138,"color":3139},{"name":3141,"color":3142},4405,"closed","InputTags max item length","2025-07-01T08:35:33Z","https://github.com/nuxt/ui/issues/4405",0.72101057,{"description":3208,"labels":3209,"number":3213,"owner":3147,"repository":3148,"state":3202,"title":3214,"updated_at":3215,"url":3216,"score":3217},"### Description\n\nThe new CheckboxGroup component lacks the `table` variant found on the RadioGroup component. Since these components will often appear together in forms, it would be preferable to have the table variant for both of them.\n\nThis is already easily achieved with the new component by adding the RadioGroup styles to the `item` ui prop. I think it should be possible to make this change just by adding the styles to checkbox-group.ts. I'm happy to make a pull request and make the changes.\n\n### Additional context\n\n_No response_",[3210,3211,3212],{"name":3138,"color":3139},{"name":3141,"color":3142},{"name":3144,"color":3145},3994,"[CheckboxGroup] Add `variant=\"table\"` to match RadioGroup variants","2025-05-13T12:28:16Z","https://github.com/nuxt/ui/issues/3994",0.7262358,{"description":3219,"labels":3220,"number":3224,"owner":3147,"repository":3148,"state":3202,"title":3225,"updated_at":3226,"url":3227,"score":3228},"### Description\n\nI want to allow multiple values selection in radio group, but cannot find any prop of way from the documentation\n\n### Additional context\n\n_No response_",[3221,3222,3223],{"name":3138,"color":3139},{"name":3141,"color":3142},{"name":3144,"color":3145},4143,"Multiple Value selection in radio group","2025-05-13T13:57:53Z","https://github.com/nuxt/ui/issues/4143",0.72887796,{"description":3230,"labels":3231,"number":3236,"owner":3147,"repository":3148,"state":3202,"title":3237,"updated_at":3238,"url":3239,"score":3240},"### Description\n\nHey there!\n\nI am currently doing migration of https://www.nuxt-commerce.dev/ from Nuxt UI 2->3 (it was so good experience - kudos to you!).\n\nI finished migrating almost everything apart from one thing - the Select component that has Nuxt Links inside. Basically the NuxtLink does not seem to work - the page is not changing after clicking (while the selected value is correctly updated to the clicked one. Do you know what could be the issue?\n\nThe code I use looks like this:\n\n```html\n\u003Ctemplate>\n \u003CUSelect\n v-model=\"selected\"\n value-key=\"value\"\n :items=\"selectOptions\"\n >\n {{ selected }}\n \u003Ctemplate #item=\"{ item }\">\n \u003CNuxtLink\n :to=\"`/collection/${item?.to}`\"\n >\n \u003Cp>{{ item?.value }}\u003C/p>\n \u003C/NuxtLink>\n \u003C/template>\n \u003C/USelect>\n\u003C/template>\n\n\n\u003Cscript setup lang=\"ts\">\nconst selectOptions = computed(() => {\n return props.collections?.edges.map(({ node }) => ({\n value: node.title,\n to: node.handle,\n }))\n})\n\nconst selected = ref(\n selectOptions.value?.find(\n option => route.params.handle && option.to === route.params.handle[0],\n )?.value,\n)\n\u003C/script>\n```",[3232,3235],{"name":3233,"color":3234},"question","d876e3",{"name":3141,"color":3142},3443,"Does Select work with NuxtLink/UI Link?","2025-03-04T09:18:16Z","https://github.com/nuxt/ui/issues/3443",0.74938285,{"description":3242,"labels":3243,"number":3246,"owner":3147,"repository":3148,"state":3202,"title":3247,"updated_at":3248,"url":3249,"score":3250},"### Description\n\nCurrently, the Select components items popover does not display a scrollbar, even though the content is scrollable. This may confuse users, as they might not realize there are additional options available beyond what is initially visible. While in some cases the partial display of the last cut-off item may hint that more options are available, it is not ideal to rely on this visual cue alone.\n\nExample from the Select Component docs:\n\nIt seems like `Broccoli` is the last item:\n\n\nBut it is not:\n\n\n### Additional context\n\nhttps://ui.nuxt.com/components/select#items",[3244,3245],{"name":3138,"color":3139},{"name":3141,"color":3142},4069,"Scrollbar for Select Component","2025-05-23T15:41:53Z","https://github.com/nuxt/ui/issues/4069",0.75294733,["Reactive",3252],{},["Set"],["ShallowReactive",3255],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fL1vAxf223qQYH8741IVaF5xoEAJGxC76y-eg-PSy-sA":-1},"/nuxt/ui/4057"]