` 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_",[2026,2029],{"name":2027,"color":2028},"enhancement","a2eeef",{"name":1991,"color":1992},2796,"UTable row click event","2025-01-23T09:56:08Z","https://github.com/nuxt/ui/issues/2796",0.720462,{"description":2036,"labels":2037,"number":2041,"owner":1994,"repository":1995,"state":2042,"title":2043,"updated_at":2044,"url":2045,"score":2046},"### Environment\n\n- Operating System: Windows 10 \n- Node Version: v22.10.0 \n- Nuxt Version: 3.16.0 \n- CLI Version: 3.22.5 \n- Nitro Version: 2.11.5 \n- Package Manager: pnpm@9.15.7 \n- Builder: -\n- User Config: compatibilityDate, devtools, modules, css, meta, ssr, runtimeConfig, ui \n- Runtime Modules: @nuxt/ui@3.0.0-beta.3, @nuxt/icon@1.10.3, @nuxt/fonts@0.11.0, @vueuse/nuxt@12.8.2\n\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nNuxt UI 3.0\n\n### Reproduction\n\n```\n\u003Ctemplate>\n\u003CUInput\n v-model=\"translation\"\n ref=\"translationField\" \n />\n\u003C/template>\n\n\u003Cscript setup>\nconst translationField = ref(null)\n\nfunction nextCard() {\n translationField.value.focus() // throws: 'focus is not a function'\n \n nextTick(() => {\n translationField.value.focus() // same error\n })\n\n // below works ok\n nextTick(() => {\n const input = translationField.value?.$el?.querySelector('input')\n if (input) {\n input.focus()\n }\n })\n}\n\u003C/script>\n```\n\n\n### Description\nStandard Vue method of using template ref (for setting a focus, here) throws: 'focus() is not a function'\nIn the above code snippet I included workaround (credits to Sonnet 3.5)\nTried it dozen of times and checked this place to see if it has not been solved earlier.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2038,2039,2040],{"name":1985,"color":1986},{"name":2015,"color":2016},{"name":1991,"color":1992},3644,"closed","\u003CUInput> template ref does not work","2025-03-21T13:14:18Z","https://github.com/nuxt/ui/issues/3644",0.665863,{"description":2048,"labels":2049,"number":2052,"owner":1994,"repository":1995,"state":2042,"title":2053,"updated_at":2054,"url":2055,"score":2056},"### Environment\n\n-\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.16.0\n\n### Reproduction\n\n- \n\n### Description\n\nUpgraded all deps to the latest and bam Nuxt 3.16.0 is added. We get errors now as Nuxt UI 3 still ships with\n\n`'@unhead/vue': 1.11.20(vue@3.5.13(typescript@5.8.2))\n`\n\nAs of Nuxt 3.16.0 ships with @unhead2:\nhttps://nuxt.com/blog/v3-16#unhead-v2\n\nActual error:\n`[@nuxt/scripts 9:42:20 PM] ERROR Nuxt Scripts requires Unhead >= 2, you are using v1.11.20. Please run nuxi upgrade --clean to upgrade...`\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2050,2051],{"name":1985,"color":1986},{"name":2015,"color":2016},3513,"Nuxt 3.16.0 - ships with @unhead2","2025-03-10T08:49:36Z","https://github.com/nuxt/ui/issues/3513",0.6856036,{"description":2058,"labels":2059,"number":2062,"owner":1994,"repository":1995,"state":2042,"title":2063,"updated_at":2064,"url":2065,"score":2066},"### Environment\n\nirrelevant\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\n\"@nuxt/ui\": \"3.0.0-alpha.9\",\n\n### Reproduction\n\n\n\n\n### Description\n\ncontributes to failing google lighthouse scores for this violation\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2060,2061],{"name":1985,"color":1986},{"name":2015,"color":2016},2725,"UBreadcrumb accessibility issue - Lists do not contain only \u003Cli> elements and script supporting elements (\u003Cscript> and \u003Ctemplate>).","2024-12-05T13:48:54Z","https://github.com/nuxt/ui/issues/2725",0.68752766,{"description":2068,"labels":2069,"number":2071,"owner":1994,"repository":1995,"state":2042,"title":2072,"updated_at":2073,"url":2074,"score":2075},"### Description\n\nSometimes is necessary to disable a component based in error validations, it would be useful to have the errors object in the default slot.\r\n\r\nThanks.\n\n### Additional context\n\n_No response_",[2070],{"name":2027,"color":2028},2155,"`UForm` errors","2024-09-12T09:14:33Z","https://github.com/nuxt/ui/issues/2155",0.6984898,{"description":2077,"labels":2078,"number":2081,"owner":1994,"repository":1995,"state":2042,"title":2082,"updated_at":2083,"url":2084,"score":2085},"### Version\n\nv3 latest commit\n\n### Description\n\nThe `size-*` class applied by a button gets overwritten by the icon itself.\n\nLeft one is in my project, right one is from the docs:\n\n\u003Cimg width=\"300\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/c1c427fd-6854-4623-b5f1-db47a74450e2\" />\n\n\u003Cimg width=\"428\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/7f2bf278-8b13-4d8b-84ec-beb29d9036bb\" />\n\nI couldnt reproduce in a fresh project, but my project is pretty clean still with no customizations. Might have something to do with the css order?\n",[2079,2080],{"name":1985,"color":1986},{"name":2015,"color":2016},2926,"v3: Icon size gets overwritten by icon's width/height","2024-12-29T11:55:14Z","https://github.com/nuxt/ui/issues/2926",0.70048887,{"description":2087,"labels":2088,"number":2093,"owner":1994,"repository":1995,"state":2042,"title":2094,"updated_at":2095,"url":2096,"score":2097},"### Environment\n\n- Operating System: `Darwin`\n- Node Version: `v20.18.3`\n- Nuxt Version: `3.15.4`\n- CLI Version: `3.22.2`\n- Nitro Version: `2.10.4`\n- Package Manager: `pnpm@9.15.4`\n- Builder: `-`\n- User Config: `extends`, `modules`, `$development`, `devtools`, `colorMode`, `runtimeConfig`, `routeRules`, `future`, `compatibilityDate`, `vite`, `typescript`, `hooks`, `echo`, `eslint`, `i18n`, `sanctum`\n- Runtime Modules: `@nuxt/content@2.13.4`, `@nuxt/eslint@0.7.6`, `@nuxt/fonts@0.10.3`, `@nuxt/image@1.9.0`, `@nuxt/ui@2.21.0`, `@nuxthq/studio@2.2.1`, `@vueuse/nuxt@12.7.0`, `nuxt-og-image@4.1.4`, `@nuxtjs/i18n@9.2.1`, `nuxt-auth-sanctum@0.5.6`, `nuxt-laravel-echo@0.2.1`, `@nuxtjs/seo@2.2.0`\n- Build Modules: `-`\n\n\n### Version\n\n2.21.0\n\n### Reproduction\n\nhttps://stackblitz.com/edit/nuxt-ui-i7bgngfx?file=app.vue\n\n### Description\n\nIf I place a USelectMenu inside a UModal that is being opened inside USlideover, I cannot focus the select menu's input.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2089,2090],{"name":1985,"color":1986},{"name":2091,"color":2092},"upstream","78bddb",3408,"USelectMenu inside UModal inside USlideover","2025-03-24T14:19:31Z","https://github.com/nuxt/ui/issues/3408",0.70289284,["Reactive",2099],{},["Set"],["ShallowReactive",2102],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"IjmUDs0GD3v6RB9I6A3JpbT3Bvj-82Zpy6iwF12f6eU":-1},"/nuxt/ui/2732"]