\n\nPerhaps a wider task should be considered to allow a custom label or icon so the user can decide if they want to override any of these extra key captures (enter/up arrow/etc). Delete also for example I would rather show the backspace icon or 'del'.\n\n### Additional context\n\n\u003Cimg width=\"713\" height=\"280\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/a3d0e2de-eb10-48cd-821f-846650de9789\" />\n\n\u003Cimg width=\"759\" height=\"385\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/c82a7252-4eaf-4faf-ba05-605486e3ae8e\" />",[3165,3166,3167],{"name":3146,"color":3147},{"name":3149,"color":3150},{"name":3152,"color":3153},4940,"Update Escape Kdb or add optional Kbd labels/icons","2025-09-10T18:22:35Z","https://github.com/nuxt/ui/issues/4940",0.74570763,{"description":3174,"labels":3175,"number":3181,"owner":3155,"repository":3156,"state":3182,"title":3183,"updated_at":3184,"url":3185,"score":3186},"### Environment\n\nhttps://ui.nuxt.com/components/button\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3\n\n### Reproduction\n\nhttps://ui.nuxt.com/components/button\n\n### Description\n\nThe Nuxt UI button component doesn't seem to have cursor pointer in version 3.\n\nVersion 2 was fine.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3176,3179,3180],{"name":3177,"color":3178},"bug","d73a4a",{"name":3149,"color":3150},{"name":3152,"color":3153},3773,"closed","Cursor pointer not used on button","2025-04-02T09:36:57Z","https://github.com/nuxt/ui/issues/3773",0.7342748,{"description":3188,"labels":3189,"number":3193,"owner":3155,"repository":3155,"state":3182,"title":3194,"updated_at":3195,"url":3196,"score":3197},"Maybe I forgot to configure something but I can't use the colon shortcut for v-bind in pages.\r\n\r\n```javascript\r\nstep(\r\n v-for=\"step in steps\"\r\n :description=\"step.description\"\r\n :key=\"step.number\"\r\n :number=\"step.number\"\r\n :title=\"step.title\"\r\n)\r\n```\r\n\r\nWill result in:\r\n\r\n```\r\nModule build failed: Error:\r\n 18| step(\r\n 19| v-for=\"step in steps\"\r\n > 20| :description=\"step.description\"\r\n--------------------^\r\n 22| :key=\"step.number\"\r\n 23| :number=\"step.number\"\r\n\r\nSyntax Error: Unexpected token\r\n```\r\n\r\nThe strange thing is that sometimes this shortcut seems to work in files within the `components` folder.\n\n\u003C!--cmty-->\u003C!--cmty_prevent_hook-->\n\u003Cdiv align=\"right\">\u003Csub>\u003Cem>This question is available on \u003Ca href=\"https://nuxtjs.cmty.io\">Nuxt.js\u003C/a> community (\u003Ca href=\"https://nuxtjs.cmty.io/nuxt/nuxt.js/issues/c1122\">#c1122\u003C/a>)\u003C/em>\u003C/sub>\u003C/div>",[3190],{"name":3191,"color":3192},"2.x","d4c5f9",1270,"Inability to use shortcut colon for v-bind in pages","2023-01-18T15:41:00Z","https://github.com/nuxt/nuxt/issues/1270",0.74054927,{"description":3199,"labels":3200,"number":3204,"owner":3155,"repository":3156,"state":3182,"title":3205,"updated_at":3206,"url":3207,"score":3208},"### Description\n\nAdd option to require a specific element to be hovered to trigger a shortcut.\n\n### Additional context\n\nIn my experience I often found it useful to limit the scope of a shortcut to specific element so that the user has to hover over the element and press so key/combination of keys.\n\nA good example could be a list of items that each has its own shortcut that will open it's detail drawer, modal... but only if the mouse is hovering the item in the list.\n\nI would like to implement this feature if it sounds interesting.",[3201,3202,3203],{"name":3146,"color":3147},{"name":3149,"color":3150},{"name":3152,"color":3153},4165,"`defineShortcuts` limit shortcut to a specific element","2025-06-11T15:47:21Z","https://github.com/nuxt/ui/issues/4165",0.7489178,{"description":3210,"labels":3211,"number":3223,"owner":3155,"repository":3155,"state":3182,"title":3224,"updated_at":3225,"url":3226,"score":3227},"### Describe the feature\n\nSeveral composable functions ( `useState`, `useFetch`, `useAsyncData`, `useLazyAsyncData`, `useLazyFetch`) provide auto-key generation that is unique to the file name and line number of the instance of function call. However, this makes it impossible to create your own wrappers around these functions, because then the auto-generated key will always be the same for any wrapper-function call.\r\n\r\n```ts\r\n// composables/useAsyncSpecifiedData.ts\r\nexport function useAsyncSpecifiedData(params) {\r\n\t// ... do some work\r\n\tconst handler = createHandler( params )\r\n\tconst options = createOptions( params )\r\n\treturn useAsyncData(handler, options) // \u003C- the unique key always generated exactly for this file+line\r\n}\r\n```\r\nI would like to have oportynity to somehow expand keyed functions with myown\r\nhttps://github.com/nuxt/framework/blob/51bc6e44fef6e4a249946ba910a497089b089a64/packages/vite/src/plugins/composable-keys.ts#L15-L17\r\n\r\nSo that nuxt will generates a unique key directly for the wrapper function call, which will be passed down in `useAsyncData`. Since it is work for `useLazyAsyncData`\r\nhttps://github.com/nuxt/framework/blob/51bc6e44fef6e4a249946ba910a497089b089a64/packages/nuxt/src/app/composables/asyncData.ts#L263-L274\n\n### Additional information\n\n- [x] Would you be willing to help implement this feature?\n- [ ] Could this feature be implemented as a module?\n\n### Final checks\n\n- [X] Read the [contribution guide](https://v3.nuxtjs.org/community/contribution).\n- [X] Check existing [discussions](https://github.com/nuxt/framework/discussions) and [issues](https://github.com/nuxt/framework/issues).",[3212,3214,3217,3220],{"name":3146,"color":3213},"8DEF37",{"name":3215,"color":3216},"good first issue","fbca04",{"name":3218,"color":3219},"3.x","29bc7f",{"name":3221,"color":3222},"🍰 p2-nice-to-have","0E8A16",12369,"Ability to add your own keyed functions ","2023-03-07T21:06:18Z","https://github.com/nuxt/nuxt/issues/12369",0.75680643,{"description":3229,"labels":3230,"number":3233,"owner":3155,"repository":3156,"state":3182,"title":3234,"updated_at":3235,"url":3236,"score":3237},"### Description\n\nUSelect displays the label of the selected value. It might be interesting to add a slot to display another key when item is an object instead of the chosen label for some use case.\n\nMy own use case is picking the language :\n\n```\nconst items = [\n { value: 'en', label: 'English' },\n { value: 'fr', label: 'Français' },\n (...)\n]\n```\n\nMy open selection would display flags and labels, but once selected, the component would only display the value ('en' or 'fr' or ...). Could be the icon as well.\n\nProposal :\n\nselectLabelKey : When items is an array of objects, select the field to use as the label for the picked value on the base component (instead of labelKey)\n\n### Additional context\n\n_No response_",[3231,3232],{"name":3146,"color":3147},{"name":3149,"color":3150},4157,"USelect base text display","2025-05-23T12:25:54Z","https://github.com/nuxt/ui/issues/4157",0.75768435,{"description":3239,"labels":3240,"number":3245,"owner":3155,"repository":3156,"state":3182,"title":3246,"updated_at":3247,"url":3248,"score":3249},"### Description\n\nThe concepts of Chips and Badges are reversed. \n\nChip is the component with text, to represent status or options selected, that can also have counters, icons aside labels and in some cases a remove button.\nBadge is the component that have a notification or a counter\n\nIn my opinion:\n\nThis is a chip ⤵️\n\n\nAnd this is a Badge ⤵️\n\n\nAn example\nhttps://medium.com/design-bootcamp/ux-blueprint-03-badges-vs-chips-tags-a-friendly-guide-e38ab2217be3#:~:text=Key%20Differences,users%20navigate%20and%20manage%20content.",[3241,3244],{"name":3242,"color":3243},"question","d876e3",{"name":3149,"color":3150},3282,"The concepts of Chips and Badges are reversed","2025-02-10T09:38:39Z","https://github.com/nuxt/ui/issues/3282",0.7601466,{"labels":3251,"number":3257,"owner":3155,"repository":3155,"state":3182,"title":3258,"updated_at":3259,"url":3260,"score":3261},[3252,3253,3254],{"name":3146,"color":3213},{"name":3218,"color":3219},{"name":3255,"color":3256},"dx","C39D69",13963,"automatically generate unique keys for keyed composables","2023-01-19T17:11:03Z","https://github.com/nuxt/nuxt/issues/13963",0.7609483,{"description":3263,"labels":3264,"number":3267,"owner":3155,"repository":3156,"state":3182,"title":3268,"updated_at":3269,"url":3270,"score":3271},"### Description\n\nI can see there was some changes [here](https://github.com/nuxt/ui/pull/3123) which is great.\n\nI'm just wondering why the 'help' property was excluded from these additions?\n\nThank you!",[3265,3266],{"name":3242,"color":3243},{"name":3149,"color":3150},3685,"Was UFormField 'help' property excluded from the aria-describedby update for any specific reason?","2025-03-26T12:47:39Z","https://github.com/nuxt/ui/issues/3685",0.76302546,["Reactive",3273],{},["Set"],["ShallowReactive",3276],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fQEHDn7IJduHVNH2qk8phBJorTuc2gw5c6KeJGrS2hxk":-1},"/nuxt/ui/3817"]