\n \u003C/template>\n\n \u003Ctemplate #item=\"{ item }\">\n \u003Cspan v-text=\"item.label\" />\n \u003C/template>\n\u003C/UDropdownMenu>\n```",[3186,3189],{"name":3187,"color":3188},"question","d876e3",{"name":3149,"color":3150},4636,"DropdownMenu keyboard interaction handling","2025-07-31T06:44:47Z","https://github.com/nuxt/ui/issues/4636",0.74348074,{"description":3196,"labels":3197,"number":3201,"owner":3155,"repository":3156,"state":3157,"title":3202,"updated_at":3203,"url":3204,"score":3205},"### 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_",[3198,3199,3200],{"name":3146,"color":3147},{"name":3149,"color":3150},{"name":3152,"color":3153},4201,"[InputNumber] Add support for leading & trailing slots","2025-05-21T13:07:28Z","https://github.com/nuxt/ui/issues/4201",0.7462362,{"description":3207,"labels":3208,"number":3211,"owner":3155,"repository":3156,"state":3157,"title":3212,"updated_at":3213,"url":3214,"score":3215},"### Description\n\n> @hasan-ozbey the mutation on `@create` is handled in your `onCreate` function, outside of `USelectMenu` component, that's why it doesn't trigger the `@change` event. I see how this can be an issue if you need to validate created items since it won't send any `input` / `change` events to the Form in this case.\n> \n> Can you create an issue so we can discuss it separately? \n\n _Originally posted by @romhml in [#3660](https://github.com/nuxt/ui/issues/3660#issuecomment-2873075460)_\n\n------\n\nBy default, the form validates when a field emits `blur`, `input`, or `change` events.\n\nSelecting an item from the search results emits `change`, triggering immediate validation. But when `onCreate` creates an item programmatically, it doesn't emit `change`, so validation is deferred until the next `blur` event.\n\n```ts\n\u003Cscript setup lang=\"ts\">\nconst selected = ref('')\n\nfunction onCreate(item: string) {\n selected.value = item\n}\n\u003C/script>\n\n\u003Ctemplate>\n \u003CUSelectMenu\n v-model=\"selected\"\n create-item\n @create=\"onCreate\"\n @change=\"console.log('CHANGE')\"\n />\n\u003C/template>\n```\n\nI think created items should emit `change` so we can validate them properly.\n\nAdditionally, because of https://github.com/nuxt/ui/issues/3736,the field always starts in an error state when a new item is created in certain conditions (regardless of whether the item meets the schema's requirements or not).\n\n------\n\nCurrent workaround is to run the validation manaully on a field after mutating the model:\n\n```ts\nasync function onCreate(item: string) {\n selected.value = item\n\n await formRef.value?.validate({ name: 'fieldName' })\n}\n```",[3209,3210],{"name":3146,"color":3147},{"name":3149,"color":3150},4139,"USelectMenu should emit 'change' after creating an item","2025-05-13T09:15:02Z","https://github.com/nuxt/ui/issues/4139",0.74905795,{"description":3217,"labels":3218,"number":3222,"owner":3155,"repository":3156,"state":3157,"title":3223,"updated_at":3224,"url":3225,"score":3226},"### Description\n\nOptions in `SelectMenu` might need a description below the title e.g. like the watch dropdown on github:\n\n\u003Cimg width=\"362\" height=\"378\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/78093701-742b-49ad-8b60-e26435a3bca5\" />\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_",[3219,3220,3221],{"name":3146,"color":3147},{"name":3149,"color":3150},{"name":3152,"color":3153},4661,"SelectMenu: add description props to show text below title","2025-08-06T02:19:32Z","https://github.com/nuxt/ui/issues/4661",0.7515184,{"description":3228,"labels":3229,"number":3232,"owner":3155,"repository":3156,"state":3157,"title":3233,"updated_at":3234,"url":3235,"score":3236},"### Package\n\nv3.18\n\n### Description\n\nHello,\nI've been using Nuxt UI for many months and I really love it!\n\nHowever, I've often run into limitations with the `InputMenu` component, because its behavior feels too close to the `SelectMenu`.\n\nThe main difference (at least for me) is that since it's an **input**, the priority should be the input value itself. But currently, it behaves more like the `SelectMenu`, where the value must exist in the provided `:items` in order to be set. The text entered in the field is only treated as a **search term**, and it is not updated in the bound **ref** — while it should be, since this is supposed to be an **input**.\n\nI think the `InputMenu` should allow any value typed by the user to be stored and displayed, even if it’s not present in the `:items` list. This would make it much more flexible and closer to the expected behavior of an **input** field.\n\nFor example, in this `InputMenu` example, if i start to type 'Hello', the **ref** value still remains 'Backlog'... \nThis is the excepted behaviour for a `SelectMenu`, but for a `InputMenu`, the **ref** value should become 'Hello':\n\n\u003Cimg width=\"583\" height=\"308\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/7fd4d063-310b-4556-a61a-20c962a4785a\" />\n\nAnd for me the `:create-item` option doesn’t solve this case, because from a UX perspective it doesn’t behave like a true **input**. The **input** value shouldn’t require extra steps to be reflected in the bound **ref**.\n\nI'm curious about your point of view, and if you agree with me, \nwould it be possible to adjust this behavior, or at least provide an option to allow free input values?\n\nThanks a lot for your work!",[3230,3231],{"name":3187,"color":3188},{"name":3149,"color":3150},4859,"InputMenu behaves like a SelectMenu instead of a true input – needs proper input behavior","2025-09-10T22:12:11Z","https://github.com/nuxt/ui/issues/4859",0.7643584,{"description":3238,"labels":3239,"number":3243,"owner":3155,"repository":3156,"state":3157,"title":3244,"updated_at":3245,"url":3246,"score":3247},"### Description\n\nFor [SelectMenu](https://ui.nuxt.com/components/select-menu) seems to be no option to customize the label of the selected item, e.g. use multiple values to compose the label. Currently only one item value can be selected by prop `labelKey`, but it is not possible to use multiple values OR to even add custom html-code.\n\n**Example:**\n\n```ts\nconst items = [\n {\n id: 1,\n firstName: 'Max',\n lastName: 'Mustermann',\n },\n ...\n]\n```\n\nThe items to select can be fully customized, even with custom html code:\n\n```vue\n\u003Ctemplate #item-label=\"{ item }\">\n {{ item.firstName }} \u003Cspan class=\"text-highlighted\">{{ item.lastName}}\u003C/span>\n \u003Cdiv class=\"text-xs text-muted\">#{{ item.customerId }}\u003C/div>\n\u003C/template>\n```\n\nBut when an item is selected, the selected item can only be one value:\n\n```vue\n\u003CUSelectMenu label-key=\"lastName\" />\n```\n\n**Possible solutions:**\n\n1. Make a new label prop that accepts a function, so values can be compound:\n\n```ts\n\u003CUSelectMenu :label=\"(item) => item.firstName + ' ' + item.lastName\"\n```\n\n2. Optionally make a slot to customize the labels: \n```vue\n\u003CUSelectMenu>\n \u003Ctemplate #label=\"{ item }\">\n {{ item.firstName }} \u003Cspan class=\"text-highlighted\">{{ item.lastName}}\u003C/span>\n \u003Cspan class=\"text-xs text-muted\">#{{ item.customerId }}\u003C/span>\n \u003C/template>\n\u003C/USelectMenu>\n```\n\nP.S. the prop `labelKey` is not documented https://ui.nuxt.com/components/select-menu#props\n",[3240,3241,3242],{"name":3146,"color":3147},{"name":3149,"color":3150},{"name":3152,"color":3153},4581,"SelectMenu: Compound label","2025-07-23T16:38:06Z","https://github.com/nuxt/ui/issues/4581",0.7664783,{"description":3249,"labels":3250,"number":3253,"owner":3155,"repository":3156,"state":3254,"title":3255,"updated_at":3256,"url":3257,"score":3258},"### Description\n\nWhen using \u003CUNavigationMenu> with onSelect (instead of to), there's no way to manually set the active state on items. It would be helpful to support an active prop or a value binding (like in buttons #3417) to reflect the selected state visually.\n\n### Additional context\n\n_No response_",[3251,3252],{"name":3146,"color":3147},{"name":3149,"color":3150},4185,"closed","Allow `active` style on `UNavigationMenu` items when using `onSelect`","2025-05-19T15:38:25Z","https://github.com/nuxt/ui/issues/4185",0.7246377,["Reactive",3260],{},["Set"],["ShallowReactive",3263],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fHayPHE7ih_lgzyFCnDYPJdkPMZw1pW1jlac0e0gzU5I":-1},"/nuxt/ui/4463"]