\n \u003CUInput v-model=\"state.name1\" placeholder=\"...\" />\n\u003C/UModal>\n```\n\nWhen a modal contains one or more input boxes, the first input box will always get focus automatically.\nIf I manually add a close button in the upper right corner, it will trigger a validation when I click it. This is not good. How can I avoid the input box getting focus when opening the modal?\n\n### Additional context\n\n\n\n\n### Logs\n\n```shell-script\n\n```",[2917,2918],{"name":2868,"color":2869},{"name":2874,"color":2875},3062,"The input box in the modal will automatically gain focus","2025-01-10T08:36:56Z","https://github.com/nuxt/ui/issues/3062",0.71347106,{"description":2925,"labels":2926,"number":2927,"owner":2877,"repository":2928,"state":2879,"title":2929,"updated_at":2930,"url":2931,"score":2932},"I've been having an issue with this module, where the fetching of font files sometimes fails during the production build. I haven't been able to create a reliable reproduction yet—it seems to happen at random.\n\nThe build is done in GitHub CI, where a Docker image is built, using Node version 18.\n\nThis is the error log from the problematic deployment:\n```\n#25 20.31 [@nuxt/fonts] ERROR Could not fetch metadata for Red Hat Display from google. fetch failed\n#25 20.31 \n#25 20.31 at Object.fetch (node:internal/deps/undici/undici:11372:11)\n#25 20.31 at process.processTicksAndRejections (node:internal/process/task_queues:95:5)\n#25 20.31 at async getFontDetails$5 (/opt/project/node_modules/.pnpm/@nuxt+fonts@0.8.0_ioredis@5.4.1_magicast@0.3.5_rollup@4.20.0_vite@5.4.3_@types+node@22.5.5_sa_d6a46d5cxhijk7lxvuwfjdzkcm/node_modules/@nuxt/fonts/dist/module.mjs:550:12)\n#25 20.31 at async cachedData (/opt/project/node_modules/.pnpm/@nuxt+fonts@0.8.0_ioredis@5.4.1_magicast@0.3.5_rollup@4.20.0_vite@5.4.3_@types+node@22.5.5_sa_d6a46d5cxhijk7lxvuwfjdzkcm/node_modules/@nuxt/fonts/dist/module.mjs:474:20)\n#25 20.31 at async Object.resolveFontFaces (/opt/project/node_modules/.pnpm/@nuxt+fonts@0.8.0_ioredis@5.4.1_magicast@0.3.5_rollup@4.20.0_vite@5.4.3_@types+node@22.5.5_sa_d6a46d5cxhijk7lxvuwfjdzkcm/node_modules/@nuxt/fonts/dist/module.mjs:511:14)\n#25 20.31 at async resolveFontFaceWithOverride (/opt/project/node_modules/.pnpm/@nuxt+fonts@0.8.0_ioredis@5.4.1_magicast@0.3.5_rollup@4.20.0_vite@5.4.3_@types+node@22.5.5_sa_d6a46d5cxhijk7lxvuwfjdzkcm/node_modules/@nuxt/fonts/dist/module.mjs:1395:26)\n#25 20.31 at async addFontFaceDeclaration (/opt/project/node_modules/.pnpm/@nuxt+fonts@0.8.0_ioredis@5.4.1_magicast@0.3.5_rollup@4.20.0_vite@5.4.3_@types+node@22.5.5_sa_d6a46d5cxhijk7lxvuwfjdzkcm/node_modules/@nuxt/fonts/dist/module.mjs:940:22)\n#25 20.31 at async Promise.all (index 0)\n#25 20.31 at async transformCSS (/opt/project/node_modules/.pnpm/@nuxt+fonts@0.8.0_ioredis@5.4.1_magicast@0.3.5_rollup@4.20.0_vite@5.4.3_@types+node@22.5.5_sa_d6a46d5cxhijk7lxvuwfjdzkcm/node_modules/@nuxt/fonts/dist/module.mjs:1013:5)\n#25 20.31 at async Object.transform (/opt/project/node_modules/.pnpm/@nuxt+fonts@0.8.0_ioredis@5.4.1_magicast@0.3.5_rollup@4.20.0_vite@5.4.3_@types+node@22.5.5_sa_d6a46d5cxhijk7lxvuwfjdzkcm/node_modules/@nuxt/fonts/dist/module.mjs:1025:17)\n#25 20.31 \n#25 20.31 \n#25 20.31 [@nuxt/fonts] WARN Could not produce font face declaration from google for font family Red Hat Display.\n#25 20.31 \n#25 42.48 ℹ ✓ 1387 modules transformed.\n```\n\nHas anyone else come across this issue? Wouldn't it be better to exit rather than continue with the build if the font fetch fails?",[],356,"fonts","Fonts sometimes missing in production build","2024-12-05T16:49:07Z","https://github.com/nuxt/fonts/issues/356",0.7411753,{"description":2934,"labels":2935,"number":2939,"owner":2877,"repository":2940,"state":2941,"title":2942,"updated_at":2943,"url":2944,"score":2945},"Redirect to `/projects` public page instead\n\nBlocked by #403 ",[2936],{"name":2937,"color":2938},"enhancement","1ad6ff",402,"nuxt.com","closed","Beta page integration `/beta`","2022-06-07T09:41:42Z","https://github.com/nuxt/nuxt.com/issues/402",0.6696681,{"description":2947,"labels":2948,"number":2908,"owner":2877,"repository":2940,"state":2941,"title":2950,"updated_at":2951,"url":2952,"score":2913},"To be discussed",[2949],{"name":2937,"color":2938},"Improve sidebar mobile navigation on second level (after click)","2022-05-20T13:10:54Z","https://github.com/nuxt/nuxt.com/issues/297",{"description":2954,"labels":2955,"number":2961,"owner":2877,"repository":2878,"state":2941,"title":2962,"updated_at":2963,"url":2964,"score":2965},"### Environment\n\n- Operating System: Darwin\n- Node Version: v22.11.0\n- Nuxt Version: 3.16.0\n- CLI Version: 3.22.5\n- Nitro Version: 2.11.6\n- Package Manager: pnpm@9.15.4\n- Builder: -\n- User Config: modules, devtools, app, css, runtimeConfig, future, compatibilityDate, telemetry, eslint\n- Runtime Modules: @nuxt/ui-pro@3.0.0, @nuxt/eslint@1.0.1, @vueuse/nuxt@12.5.0, @nuxt/image@1.9.0\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3\n\n### Reproduction\n\nSee below\n\n### Description\n\nHey,\n\nIn UI2 when placing a UAvatar (which often is done for a user dropdown) in the DropdownMenu - clicking the Dropdown menu would trigger opening the dropdown.\nBased on UI3 docs it seems that it should work since it says Button or any other element - however this doesnt work\n\n### Additional context\n\n```ts\n\u003CUDropdownMenu :items=\"accountItems\">\n \u003CUAvatar\n v-if=\"session && session.user\"\n :src=\"session.user.image ? session.user.image : undefined\"\n :alt=\"session.user.name\"\n size=\"md\"\n />\n\u003C/UDropdownMenu>\n```\n\n### Logs\n\n```shell-script\n\n```",[2956,2957,2960],{"name":2868,"color":2869},{"name":2958,"color":2959},"needs reproduction","CB47CF",{"name":2871,"color":2872},3546,"`UAvatar` doesn't trigger `UDropdownMenu`","2025-03-28T17:43:01Z","https://github.com/nuxt/ui/issues/3546",0.7171521,{"description":2967,"labels":2968,"number":2975,"owner":2877,"repository":2878,"state":2941,"title":2976,"updated_at":2977,"url":2978,"score":2979},"### For what version of Nuxt UI are you suggesting this?\n\nv3-alpha\n\n### Description\n\nI've defined my custom color in `app.vue`:\n```\n\u003Cstyle>\n@theme {\n --color-foobar-50: #f3f1ff;\n --color-foobar-100: #ebe5ff;\n...\n```\nand defined this as primary color in `app.config.ts`:\n```\nexport default defineAppConfig({\n ui: {\n colors: {\n primary: 'foobar',\n...\n```\n\nThis causes a type error:\n> Type '\"foobar\"' is not assignable to type 'Color | undefined'.\n\nThe only workaround seems to be `'foobar' as any`. However, I'd like to avoid both `as` and `any` in my code base.\n\n### Additional context\n\n_No response_",[2969,2972,2974],{"name":2970,"color":2971},"duplicate","cfd3d7",{"name":2937,"color":2973},"a2eeef",{"name":2871,"color":2872},2531,"Allow custom colors in app.config.ts","2024-11-13T12:09:04Z","https://github.com/nuxt/ui/issues/2531",0.7177097,["Reactive",2981],{},["Set"],["ShallowReactive",2984],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fln11kzOHvoOzB5aaOjxf6iy42tXfrQKgLHlG6nDYSaQ":-1},"/nuxt/scripts/334"]