\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```",[2955,2956,2957],{"name":2928,"color":2929},{"name":2931,"color":2932},{"name":2934,"color":2935},3644,"\u003CUInput> template ref does not work","2025-03-21T13:14:18Z","https://github.com/nuxt/ui/issues/3644",0.7051631,{"description":2964,"labels":2965,"number":2970,"owner":2905,"repository":2937,"state":2947,"title":2971,"updated_at":2972,"url":2973,"score":2974},"### Description\n\nHey!\n\nIt would be nice to have the primary/secondary/neutral/etc colours defined in `app.config.ts` directly as tailwind variables (ex: text-primary-500)\n\nRight now we have to define the colours both in `app.config.ts` and `tailwind.config.js` to be able to do that. (the new `main.css` would require to create a variable for each sub-colour manually so not worth using it) \n\nFor `neutral`, since it's a tailwind colour, it could be named `text-neutr-500`\nOr maybe name all colours with something like `text-Uneutral-500`\n\n\n### Additional context\n\n_No response_",[2966,2969],{"name":2967,"color":2968},"enhancement","a2eeef",{"name":2931,"color":2932},2948,"Add theme colors as tailwind variables","2025-02-06T16:29:04Z","https://github.com/nuxt/ui/issues/2948",0.7111583,{"description":2976,"labels":2977,"number":2982,"owner":2905,"repository":2937,"state":2947,"title":2983,"updated_at":2984,"url":2985,"score":2986},"### Description\nThe current implementation of Nested forms in nuxt ui uses flex as a way to differentiate between row forms.\n\nI am currently trying to use Nuxt UI v2 UTable component with the UForm component. \n\nHowever, a more ideal situation for me would be an implementation that uses the features of Nuxt UI's table with the nested Uform component. Meaning I can have the benefits of nuxt ui's form validation as well as the table.\n\n[The implementation here would be awesome](https://stackoverflow.com/questions/6707386/add-form-to-table-rows). A more ideal implentation is [this](https://jsfiddle.net/ZRQPP/), but with the form validation features that nuxt ui provides ",[2978,2979],{"name":2916,"color":2917},{"name":2980,"color":2981},"stale","ededed",3171,"[Table] with row [Form] component features.","2025-03-09T13:19:00Z","https://github.com/nuxt/ui/issues/3171",0.7119203,{"labels":2988,"number":2998,"owner":2905,"repository":2905,"state":2947,"title":2999,"updated_at":3000,"url":3001,"score":3002},[2989,2992,2995],{"name":2990,"color":2991},"available soon","6de8b0",{"name":2993,"color":2994},"pending triage","E99695",{"name":2996,"color":2997},"2.x","d4c5f9",7648,"Full-static generated site 404 & then accessing asyncdata","2023-01-22T15:36:01Z","https://github.com/nuxt/nuxt/issues/7648",0.7140231,{"description":3004,"labels":3005,"number":3008,"owner":2905,"repository":2906,"state":2947,"title":3009,"updated_at":3010,"url":3011,"score":3012},"Hover color should be green on `ProseA`\n\n\n\nReading [typography tokens](https://github.com/nuxt-themes/typography/blob/main/tokens.config.ts), colors should be declared inside `tokens.config.ts` this way.\n\n(Tried with `colors` and `color`, both don't work)\n\n```js\nexport default defineTheme({\n typography: {\n color: {\n // palette() returns the good color scheme\n primary: palette('#00dc82')\n }\n }\n})\n```",[3006],{"name":2928,"color":3007},"ff281a",1076,"[Typography] ProseA hover color not applied","2023-06-06T12:14:34Z","https://github.com/nuxt/nuxt.com/issues/1076",0.7225268,{"description":3014,"labels":3015,"number":3018,"owner":2905,"repository":2905,"state":2947,"title":3019,"updated_at":3020,"url":3021,"score":3022},"### Version\n\n[v2.0.0](https://github.com/nuxt.js/releases/tag/v2.0.0)\n\n### Reproduction link\n\n[https://codesandbox.io/s/o96v4m0k76](https://codesandbox.io/s/o96v4m0k76)\n\n### Steps to reproduce\n\n1. Add `plugins/global.js` and import `Vue` and a component.\n2. Register the component with `Vue.component('my-comp', Component)`\n3. Add `plugins: [ '@/plugins/global.js' ]`in `nuxt.config.js`\n4. Use `\u003Cmy-comp>\u003C/my-comp>`\n\n### What is expected ?\n\nComponent should be registered with Vue and can be used globally.\n\n### What is actually happening?\n\nErrors shown.\n\n\n```\n- [Vue warn]: The client-side rendered virtual DOM tree is not matching server-rendered content.\n- [Vue warn]: Unknown custom element: \u003Cmy-comp> - did you register the component correctly?\n```\n\n\u003C!--cmty-->\u003C!--cmty_prevent_hook-->\n\u003Cdiv align=\"right\">\u003Csub>\u003Cem>This bug report is available on \u003Ca href=\"https://cmty.app/nuxt\">Nuxt\u003C/a> community (\u003Ca href=\"https://cmty.app/nuxt/nuxt.js/issues/c7863\">#c7863\u003C/a>)\u003C/em>\u003C/sub>\u003C/div>",[3016,3017],{"name":2993,"color":2994},{"name":2996,"color":2997},4006,"Global components registered with plugins is not loaded on client side","2023-01-22T15:30:07Z","https://github.com/nuxt/nuxt/issues/4006",0.7247966,["Reactive",3024],{},["Set"],["ShallowReactive",3027],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fTSMl1FXVSeidgUWYA-rkmlhzVLAVO1obMtpqO-WEx5Q":-1},"/nuxt/test-utils/583"]