` rows. `@select` brings you part of the way there, but doesn't make it easy to get access to the full underlying event, for example to check if the user is holding the \u003Ckey>Ctrl\u003C/key>.\n\nSimilarly, even with `@select` I can't see any easy way to focus the table rows using keyboard input. \n\n### Additional context\n\n_No response_",[2950,2951,2952,2953],{"name":2905,"color":2906},{"name":2908,"color":2909},{"name":2911,"color":2912},{"name":2914,"color":2912},2796,"closed","UTable row click event","2025-06-18T09:05:27Z","https://github.com/nuxt/ui/issues/2796",0.6328587,{"description":2961,"labels":2962,"number":2967,"owner":2916,"repository":2917,"state":2955,"title":2968,"updated_at":2969,"url":2970,"score":2971},"### For what version of Nuxt UI are you suggesting this?\n\nv2.x\n\n### Description\n\nTo control the rows of the table, I need a slot for them. For instance, if I want to implement a reorder feature using drag and drop, I require a \u003Ctr> element to loop through.\n\n### Additional context\n\n_No response_",[2963,2964,2965,2966],{"name":2905,"color":2906},{"name":2908,"color":2909},{"name":2911,"color":2912},{"name":2914,"color":2912},2685,"[UTable] Add the functionality to include a slot for all \u003Ctr> elements, as well as a 'default' slot.","2025-06-18T09:05:45Z","https://github.com/nuxt/ui/issues/2685",0.6817255,{"description":2973,"labels":2974,"number":2976,"owner":2916,"repository":2917,"state":2955,"title":2977,"updated_at":2978,"url":2979,"score":2980},"### For what version of Nuxt UI are you suggesting this?\n\nv2\n\n### Description\n\nPlease export `UTable` types in '#ui/types' too (Rows/Columns types).\nThanks\n\n### Additional context\n\n_No response_",[2975],{"name":2905,"color":2906},2373,"UTable types","2024-10-15T09:05:21Z","https://github.com/nuxt/ui/issues/2373",0.7158529,{"description":2982,"labels":2983,"number":2988,"owner":2916,"repository":2917,"state":2955,"title":2989,"updated_at":2990,"url":2991,"score":2992},"### For what version of Nuxt UI are you suggesting this?\n\nv2.x\n\n### Description\n\nHi I would like to have within the component UselectMenu emit the event \"scroll\" \nwith the following properties: \n```\n{\n target: HTMLElement, \n currentTarget: HTMLElement, \n scrollTop: number,\n scrollHeight: number, \n clientHeight: number, \n}\n```\n\n to dynamically remote search items through an api and append it dynamically to my USelectMenu to create an infinite scroll. \n\nThis feature would be great in both version :)\n\n### Additional context\n\n_No response_",[2984,2985,2986,2987],{"name":2905,"color":2906},{"name":2908,"color":2909},{"name":2911,"color":2912},{"name":2914,"color":2912},2793,"add an emit \"scroll\" event for USelectMenu","2025-06-18T09:05:29Z","https://github.com/nuxt/ui/issues/2793",0.72350854,{"description":2994,"labels":2995,"number":2999,"owner":2916,"repository":2917,"state":2955,"title":3000,"updated_at":3001,"url":3002,"score":3003},"### Description\n\nHi is it possible to add context menu in utable upon selecting a row ? or any alternative ways how to do it thru context menu and utable ?\n\nThankss.\n\n### Additional context\n\n_No response_",[2996,2997,2998],{"name":2905,"color":2906},{"name":2928,"color":2929},{"name":2908,"color":2909},4381,"[UTable] -> Context Menu upon selecting row","2025-06-24T12:32:01Z","https://github.com/nuxt/ui/issues/4381",0.7263334,{"description":3005,"labels":3006,"number":3013,"owner":2916,"repository":2916,"state":2955,"title":3014,"updated_at":3015,"url":3016,"score":3017},"### Environment\r\n\r\n- Operating System: `Darwin`\r\n- Node Version: `v18.18.2`\r\n- Nuxt Version: `3.6.1`\r\n- Nitro Version: `2.5.2`\r\n- Package Manager: `npm@9.8.1`\r\n- Builder: `vite`\r\n- User Config: `ssr`, `nitro`, `app`, `modules`, `security`, `vite`\r\n- Runtime Modules: `nuxt-security@1.0.0-rc.2`, `nuxt-vitest@0.10.2`\r\n- Build Modules: `-`\r\n\r\n\r\nAlthough we are pinned at Nuxt v3.6.1 'for reasons' the bug can be observed in StackBlitz repro on Nuxt v3.8.2\r\n\r\n### Reproduction\r\n\r\nhttps://stackblitz.com/edit/github-6rrfcj?file=pages%2Findex.vue\r\n\r\nNote: Issue relates to keyboard navigation! - not mouse.\r\n\r\n- Open `index` page and tab bring focus to button labelled `Goto Two`. \r\n- Hit enter key to effectively `click` button. (remember, keyboard - not mouse!)\r\n- Browser navigates to page `two`\r\n\r\nNotice the header suggests that the function `handleNext` has been called. This suggest that the `@keyup` event has fired on the `input` control on page `two` as `handleNext` is the function handling of that event. I can't think why this should be expected behaviour. Almost as if the `keyup` event from pressing the button on the `index` page is being seen by page `two` when the `focus()` call is made?! \r\n\r\nOpen the browser devtools to see console.log messages also indicating that `handleNext` has been called.\r\n\r\nAlso, to add additional context/relevant to help diagnose the error. In the script for `two.vue` there is another option (2) that can be uncommented and option (1) commented out. This only calls `focus()` after a delay. With this in place the potential bug doesn't happen.\r\n\r\n### Describe the bug\r\n\r\nI'm seeing what I think maybe a bug when navigating to a page that combines and `input` control with an associated `@keyup` handler that is also focused on page load via `onMounted` lifecycle event.\r\n\r\nFollow the reproduction above and also the effect of delaying the call to `focus()` on the `input` control.\r\n\r\n\r\n### Additional context\r\n\r\nChanging the event type on the `input` field from `@keyup` to `@keydown` also avoids the issue.\r\n\r\n### Logs\r\n\r\n_No response_",[3007,3010],{"name":3008,"color":3009},"3.x","29bc7f",{"name":3011,"color":3012},"pending triage","E99695",24434,"Unexpected @keyup triggering on focused input field when navigated to via keyboard \"click\"","2023-11-28T14:35:12Z","https://github.com/nuxt/nuxt/issues/24434",0.7274415,{"description":3019,"labels":3020,"number":3025,"owner":2916,"repository":2917,"state":2955,"title":3026,"updated_at":3027,"url":3028,"score":3029},"### Description\r\n\r\nHi 👋🏻 \r\n\r\nI started using NuxtUI and realized one more thing that can be improved. Right now, For `v-model` of tabs component index (number) is used.\r\n\r\nIf we want to get the key of active tab for making API req then we have to do something like below:\r\n```ts\r\nconst activeTabKey = items[itemsModel.value]!.key\r\n\r\n// With this feature implemented we can directly use `itemsModel.value`\r\n```\r\n\r\nInstead, if we can allow using `key` then:\r\n- I'll be more readable\r\n- If we change the order of the tabs (in items array) it doesn't affect the active tab\r\n\r\n### Additional context\r\n\r\nWe can also introduce this change in v3.",[3021,3022,3023,3024],{"name":2905,"color":2906},{"name":2908,"color":2909},{"name":2911,"color":2912},{"name":2914,"color":2912},2061,"Allow using tab item key as value for v-model","2025-06-18T09:06:22Z","https://github.com/nuxt/ui/issues/2061",0.7385614,["Reactive",3031],{},["Set"],["ShallowReactive",3034],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fp_99x49iftwIrsN8niai8IM0HpI9fkz91RX7R2e58oM":-1},"/nuxt/ui/2851"]