\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```",[2032,2033],{"name":1985,"color":1986},{"name":2021,"color":2022},3062,"The input box in the modal will automatically gain focus","2025-01-10T08:36:56Z","https://github.com/nuxt/ui/issues/3062",0.7362267,{"description":2040,"labels":2041,"number":2045,"owner":1988,"repository":2024,"state":1990,"title":2046,"updated_at":2047,"url":2048,"score":2049},"### Environment\n\n- Operating System: `Windows_NT`\n- Node Version: `v22.13.1`\n- Nuxt Version: `3.16.1`\n- CLI Version: `3.23.1`\n- Nitro Version: `2.11.7`\n- Package Manager: `yarn@1.22.22`\n- Builder: `-`\n- User Config: `compatibilityDate`, `extends`, `modules`, `css`, `app`, `linkChecker`, `build`, `schemaOrg`, `sitemap`, `robots`, `future`, `runtimeConfig`, `imports`, `ui`, `image`, `dayjs`, `prismic`\n- Runtime Modules: `@nuxtjs/prismic@4.1.0`, `nuxt-swiper@2.0.0`, `dayjs-nuxt@2.1.11`, `@nuxt/ui@3.0.0`, `@zadigetvoltaire/nuxt-gtm@0.0.13`, `@nuxtjs/seo@3.0.1`, `@nuxt/scripts@0.11.2`\n- Build Modules: `-`\n\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\n3.0.0\n\n### Reproduction\n\nnot needed\n\n### Description\n\nThe header with a lot of text in mobile is getting squashed. I believe the problem is the min-h-16 utility.\n\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2042,2043,2044],{"name":1985,"color":1986},{"name":2018,"color":2019},{"name":2021,"color":2022},3635,"UModal Header height clipped","2025-03-20T13:20:49Z","https://github.com/nuxt/ui/issues/3635",0.7384951,{"description":2051,"labels":2052,"number":2053,"owner":1988,"repository":2054,"state":1990,"title":2055,"updated_at":2056,"url":2057,"score":2058},"https://nuxt.com/deploy/firebase uses the old Firebase logo. The new logo can be found here: https://firebase.google.com/brand-guidelines\n\nI'd submit a PR, but I'm not sure where the actual image file sits, I just see a reference in the frontmatter:\n\nhttps://github.com/nuxt/nuxt.com/blob/878220e4ba9d3eaf2843f1b058bc29cc0c803e5a/content/deploy/firebase.md?plain=1#L4",[],1862,"nuxt.com","Update Firebase logo","2025-04-17T14:11:03Z","https://github.com/nuxt/nuxt.com/issues/1862",0.74249995,{"description":2060,"labels":2061,"number":2062,"owner":1988,"repository":2063,"state":2064,"title":2065,"updated_at":2066,"url":2067,"score":2068},"**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.4445639,{"description":2070,"labels":2071,"number":1987,"owner":1988,"repository":2054,"state":2064,"title":2075,"updated_at":2076,"url":2077,"score":1994},"To be discussed",[2072],{"name":2073,"color":2074},"enhancement","1ad6ff","Improve sidebar mobile navigation on second level (after click)","2022-05-20T13:10:54Z","https://github.com/nuxt/nuxt.com/issues/297",{"description":2079,"labels":2080,"number":2090,"owner":1988,"repository":1988,"state":2064,"title":2091,"updated_at":2092,"url":2093,"score":2094},"### 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_",[2081,2084,2087],{"name":2082,"color":2083},"types","2875C3",{"name":2085,"color":2086},"3.x","29bc7f",{"name":2088,"color":2089},"upstream","E8A36D",20010,"Empty global components props typings","2023-10-22T09:01:34Z","https://github.com/nuxt/nuxt/issues/20010",0.69287235,["Reactive",2096],{},["Set"],["ShallowReactive",2099],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"MA3yxd_02DK4pYJ6kVB8qkqGYwx1XY0W1WqXwvyKKIA":-1},"/nuxt/icon/270"]