\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```",[2906,2907],{"name":2868,"color":2869},{"name":2895,"color":2896},3062,"The input box in the modal will automatically gain focus","2025-01-10T08:36:56Z","https://github.com/nuxt/ui/issues/3062",0.72686744,{"description":2914,"labels":2915,"number":2916,"owner":2871,"repository":2917,"state":2918,"title":2919,"updated_at":2920,"url":2921,"score":2922},"**Environment:**\r\n- **Node Version:** v18.20.3\r\n- **Nuxt Version:** ^3.13.0\r\n- **@nuxt/fonts Version:** ^0.8.0\r\n- **Package Manager:** pnpm 9.6.0\r\n\r\n**Description:**\r\nI am experiencing an issue with the font definitions generated by the `@nuxt/font` package in my Nuxt 3 application. The package generates CSS that improperly uses the `local()` function in the `src` property of the `@font-face` declarations, causing the fonts to not load correctly.\r\n\r\n**Generated CSS Snippet:**\r\n```css\r\n@font-face {\r\n font-display: swap;\r\n font-family: 'Archivo';\r\n font-weight: 300;\r\n src: local(\"url('/fonts/Archivo-Light.woff2')\");\r\n}\r\n\r\n/* Other generated font definitions... */\r\n```\r\n\r\n**Expected Behavior:**\r\nThe fonts should load correctly without any issues.\r\n\r\n**Actual Behavior:**\r\nThe generated CSS prevents the fonts from loading properly due to the incorrect syntax in the `src` property.\r\n\r\n**Nuxt Configuration:**\r\n```ts\r\nfonts: {\r\n defaults: {\r\n styles: [\"normal\"],\r\n },\r\n families: [\r\n {\r\n name: \"Archivo\",\r\n src: \"url('/fonts/Archivo-Light.woff2')\",\r\n global: true,\r\n weight: 300\r\n },\r\n {\r\n name: \"Archivo\",\r\n src: \"url('/fonts/Archivo-Regular.woff2')\",\r\n global: true,\r\n weight: 400\r\n },\r\n {\r\n name: \"Archivo\",\r\n src: \"url('/fonts/Archivo-Medium.woff2')\",\r\n global: true,\r\n weight: 500\r\n },\r\n {\r\n name: \"Archivo\",\r\n src: \"url('/fonts/Archivo-SemiBold.woff2')\",\r\n global: true,\r\n weight: 600\r\n },\r\n {\r\n name: \"Clash Display\",\r\n src: \"url('/fonts/ClashDisplay-Regular.woff2')\",\r\n global: true,\r\n weight: 400\r\n },\r\n {\r\n name: \"Clash Display\",\r\n /*\r\n Even when i following the docs with this format (no quote)\r\n src: { name: 'Other Font', src: 'url(/fonts/ClashDisplay-Medium.woff2)', weight: 'bold' }\r\n */\r\n src: \"url('/fonts/ClashDisplay-Medium.woff2')\",\r\n global: true,\r\n weight: 500\r\n },\r\n ]\r\n }\r\n```\r\n\r\n**Steps to Reproduce:**\r\n1. Install `@nuxt/font` using pnpm.\r\n2. Configure the module in `nuxt.config.js` with the provided font settings.\r\n3. Run the application.\r\n\r\n**Additional Context:**\r\n- The paths to the font files are correct, but the current usage of `local()` in the generated CSS is causing loading issues.\r\n- A potential fix could be to modify the generated CSS to remove `local()` and use `url()` directly:\r\n ```css\r\n src: url('/fonts/Archivo-Light.woff2') format('woff2');\r\n ```\r\n\r\nThank you for your assistance!\r\n@danielroe ",[],270,"fonts","closed","Problem with @nuxt/font Usage","2024-09-23T10:29:01Z","https://github.com/nuxt/fonts/issues/270",0.45241454,{"description":2924,"labels":2925,"number":2870,"owner":2871,"repository":2929,"state":2918,"title":2930,"updated_at":2931,"url":2932,"score":2877},"To be discussed",[2926],{"name":2927,"color":2928},"enhancement","1ad6ff","nuxt.com","Improve sidebar mobile navigation on second level (after click)","2022-05-20T13:10:54Z","https://github.com/nuxt/nuxt.com/issues/297",{"description":2934,"labels":2935,"number":2937,"owner":2871,"repository":2929,"state":2918,"title":2938,"updated_at":2939,"url":2940,"score":2941},"Redirect to `/projects` public page instead\n\nBlocked by #403 ",[2936],{"name":2927,"color":2928},402,"Beta page integration `/beta`","2022-06-07T09:41:42Z","https://github.com/nuxt/nuxt.com/issues/402",0.68472606,{"description":2943,"labels":2944,"number":2950,"owner":2871,"repository":2898,"state":2918,"title":2951,"updated_at":2952,"url":2953,"score":2954},"### 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```",[2945,2946,2949],{"name":2868,"color":2869},{"name":2947,"color":2948},"needs reproduction","CB47CF",{"name":2892,"color":2893},3546,"`UAvatar` doesn't trigger `UDropdownMenu`","2025-03-28T17:43:01Z","https://github.com/nuxt/ui/issues/3546",0.69448406,{"description":2956,"labels":2957,"number":2967,"owner":2871,"repository":2871,"state":2918,"title":2968,"updated_at":2969,"url":2970,"score":2971},"### Environment\n\n- Operating System: `Darwin`\r\n- Node Version: `v16.18.1`\r\n- Nuxt Version: `3.3.2`\r\n- Nitro Version: `2.3.2`\r\n- Package Manager: `npm@8.19.2`\r\n- Builder: `vite`\r\n- User Config: `-`\r\n- Runtime Modules: `-`\r\n- Build Modules: `-`\r\n\n\n### Reproduction\n\nhttps://github.com/niklv/nuxt-component-props-def-bug\n\n### Describe the bug\n\nFor my project config typing I need to refer to typing of component props.\r\nI try extract props typing in this way. But looks like there are no props typing at all.\r\n```vue\r\n\u003Cscript lang=\"ts\" setup>\r\n// ComponentA.vue\r\nconst {propA} = defineProps\u003C{\r\n propA: string\r\n}>()\r\n\u003C/script>\r\n\r\n\u003Ctemplate>\r\n \u003Cdiv v-text=\"propA\" />\r\n\u003C/template>\r\n\r\n```\r\n\r\n```ts\r\n// config.ts\r\nimport type {ComponentA} from \"#components\";\r\nimport {ComponentOptionsBase} from \"@vue/runtime-core\";\r\n\r\n\r\ntype ComponentProps\u003CT> = T extends ComponentOptionsBase\u003Cinfer P, // Props\r\n any, // RawBindings\r\n any, // D\r\n any, // C\r\n any, // M\r\n any, // Mixin\r\n any, // Extends\r\n any> ? unknown extends P ? {} : P : {};\r\n\r\n\r\ntype CompAProps = ComponentProps\u003Ctypeof ComponentA>\r\n\r\n\r\nconst someConfig:CompAProps = {\r\n // @ts-expect-error\r\n notExistedProp: true // should be error\r\n}\r\n```\n\n### Additional context\n\n\r\n\r\nThere are must be some props typing in first generic argument of `DefineComponent`\n\n### Logs\n\n_No response_",[2958,2961,2964],{"name":2959,"color":2960},"types","2875C3",{"name":2962,"color":2963},"3.x","29bc7f",{"name":2965,"color":2966},"upstream","E8A36D",20010,"Empty global components props typings","2023-10-22T09:01:34Z","https://github.com/nuxt/nuxt/issues/20010",0.69494706,{"labels":2973,"number":2977,"owner":2871,"repository":2871,"state":2918,"title":2978,"updated_at":2979,"url":2980,"score":2981},[2974],{"name":2975,"color":2976},"2.x","d4c5f9",7221,"Bug in the code (using Vue instead of Vue.prototype)","2023-01-18T15:36:21Z","https://github.com/nuxt/nuxt/issues/7221",0.7255854,["Reactive",2983],{},["Set"],["ShallowReactive",2986],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fMA3yxd_02DK4pYJ6kVB8qkqGYwx1XY0W1WqXwvyKKIA":-1},"/nuxt/icon/270"]