\n \u003C/div>\n \u003C/UPageColumns>\n \u003C/ULandingSection>\n \u003Ctemplate #footer>\n \u003CUUser v-bind=\"testimonial.author\" size=\"xl\" :ui=\"{ description: 'line-clamp-1' }\" />\n \u003C/template>\n \u003C/UPageCard>\n \u003C/UPageMarquee>\n```\n\nHowever, when I use marquee like this, , there are no performance issues : \n\n```\n\u003CUPageSection>\n \u003CUPageLogos marquee :title=\"page.logos.title\">\n \u003Ctemplate v-for=\"image in page.logos.images\" :key=\"image.src\">\n \u003CNuxtImg\n :src=\"image.src\"\n :alt=\"image.alt\"\n :width=\"image.width\"\n :height=\"image.height\"\n loading=\"lazy\"\n sizes=\"xs:320px sm:640px md:768px\"\n quality=\"40\"\n class=\"mb-4 sm:mb-0 sm:mr-4 mx-auto flex-shrink-0\"\n />\n \u003C/template>\n \u003C/UPageLogos>\n \u003C/UPageSection>\n```\n\nI have the impression that in one case, the animation loading is deferred, whereas in the other, it is not.",[1984,1987,1990,1993],{"name":1985,"color":1986},"bug","d73a4a",{"name":1988,"color":1989},"v3","49DCB8",{"name":1991,"color":1992},"pro","5BD3CB",{"name":1994,"color":1995},"triage","ffffff",3454,"nuxt","ui","open","PageMarquee with testimonials have performance trouble","2025-03-09T20:39:12Z","https://github.com/nuxt/ui/issues/3454",0.740692,{"description":2005,"labels":2006,"number":2011,"owner":1997,"repository":2012,"state":1999,"title":2013,"updated_at":2014,"url":2015,"score":2016},"### Environment\n\n- Operating System: Darwin\n- Node Version: v20.16.0\n- Nuxt Version: 3.13.2\n- CLI Version: 3.15.0\n- Nitro Version: 2.9.7\n- Package Manager: pnpm@9.12.1\n- Builder: -\n- User Config: default\n- Runtime Modules: @nuxt/test-utils/module@3.14.4\n- Build Modules: -\n\n\n### Reproduction\n\nCreate a new Nuxt projet, install test suite following [this link](https://nuxt.com/docs/getting-started/testing)\nCreate a simple test and run pnpm dev. \n\nOpen devtools and run the tests\n\n\n### Describe the bug\n\nTests run from the devtools or the Vitest UI url on `pnpm dev` are broken with `TypeError: Cannot read properties of undefined (reading 'vueApp')\n`\n\n\n\nHowever, running `vitest --ui `manually is working\n\n\n\n### Additional context\n\nThis happens even with the most basic vitest config file and nuxt config\n```typescript\nimport { fileURLToPath } from 'node:url'\nimport { defineVitestConfig } from '@nuxt/test-utils/config'\n\nexport default defineVitestConfig({\n test: {\n environment: 'nuxt',\n },\n})\n\n``` \n\n```typescript\n// https://nuxt.com/docs/api/configuration/nuxt-config\nexport default defineNuxtConfig({\n compatibilityDate: '2024-04-03',\n devtools: { enabled: true },\n modules: [\n '@nuxt/test-utils/module'\n ]\n})\n\n``` \n\nSpec file: \n```typescript\nimport { it } from 'vitest'\nimport { mountSuspended } from '@nuxt/test-utils/runtime'\nimport App from '../app.vue'\n\nit('can mount some component', async () => {\n await mountSuspended(App)\n})\n\n``` \n\nSince test are working by running `vitest --ui` it isn't blocking but it kinda defeat the whole purpose of using `@nuxt/test-utils/module`, which seemed very convenient\n\n### Logs\n\n_No response_",[2007,2008],{"name":1985,"color":1986},{"name":2009,"color":2010},"good first issue","7057ff",989,"test-utils","Testing in devtools fails","2025-02-11T15:10:14Z","https://github.com/nuxt/test-utils/issues/989",0.76585037,{"description":2018,"labels":2019,"number":2023,"owner":1997,"repository":1998,"state":1999,"title":2024,"updated_at":2025,"url":2026,"score":2027},"### Environment\n\n- Operating System: `Darwin`\n- Node Version: `v22.1.0`\n- Nuxt Version: `3.16.2`\n- CLI Version: `3.24.0`\n- Nitro Version: `2.11.8`\n- Package Manager: `yarn@4.7.0`\n- Builder: `-`\n- User Config: `modules`, `ssr`, `components`, `app`, `css`, `runtimeConfig`, `compatibilityDate`, `nitro`, `vite`, `eslint`\n- Runtime Modules: `@pinia/nuxt@0.10.1`, `pinia-plugin-persistedstate/nuxt@4.2.0`, `@nuxt/ui@3.0.2`, `dayjs-nuxt@2.1.11`, `@nuxt/eslint@1.3.0`\n- Build Modules: `-`\n\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\n3.0.2\n\n### Reproduction\n\nhttps://codesandbox.io/p/sandbox/festive-feather-mzq49q\n\nIn the second select (which is wrapped in a form tag), don't select anything, and click save to submit the form.\n\nIt should show the browser \"this input is required\" tooltip.\n\n### Description\n\nI can't really understand why/how this happens. Sometimes, the `required` prop on a Select component will not prevent the form to be submitted. But sometimes it's working fine.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2020,2021,2022],{"name":1985,"color":1986},{"name":1988,"color":1989},{"name":1994,"color":1995},3882,"Select required sometimes not working","2025-04-14T08:11:48Z","https://github.com/nuxt/ui/issues/3882",0.7662804,{"description":2029,"labels":2030,"number":2031,"owner":1997,"repository":2032,"state":2033,"title":2034,"updated_at":2035,"url":2036,"score":2037},"# Issue\nInitial browsing to `http://localhost:3000` in **dev mode** will get error page:\n\n\n\n# Dev Environment\n- OS: **Windows 10 x64**\n- Browser: **Microsoft Edge**\n- nodejs: **v20.18.2**\n- pnpm: **9.15.4**\n\n\n\n# Repro\n1. Follow setup instructions of `README.md`\n2. Execute `pnpm dev`\n\n\n\n3. Open browser on `http://localhost:3000/` will come up with server error log and according browser view:\n\n\n\n\n\n# Fix / Analysis\n**Update by 10-Feb-2025:**\nA dependency upgrade to Nuxt 3.15.4 will resolve that issue. It looks that the root cause has been fixed by this [Nuxt PR](https://github.com/nuxt/nuxt/pull/30802).\nPR #1784 resolves this issue.",[],1783,"nuxt.com","closed","500 error on landing page route \"/\" in dev mode caused by emojilib","2025-03-21T19:06:05Z","https://github.com/nuxt/nuxt.com/issues/1783",0.7266185,{"description":2039,"labels":2040,"number":2044,"owner":1997,"repository":1997,"state":2033,"title":2045,"updated_at":2046,"url":2047,"score":2048},"When I visit my page on mobile, the \u003Chtml> tag width cannot full screen, see the image:\r\n\r\n\r\n\r\nIt seems html width is always 784px when the mobile screen less than 784px.\r\n(ps: I deleted { name: 'viewport', content: 'width=device-width, initial-scale=1' } in nuxt.config.js file)\n\n\u003C!--cmty-->\u003C!--cmty_prevent_hook-->\n\u003Cdiv align=\"right\">\u003Csub>\u003Cem>This question is available on \u003Ca href=\"https://nuxtjs.cmty.io\">Nuxt.js\u003C/a> community (\u003Ca href=\"https://nuxtjs.cmty.io/nuxt/nuxt.js/issues/c1912\">#c1912\u003C/a>)\u003C/em>\u003C/sub>\u003C/div>",[2041],{"name":2042,"color":2043},"2.x","d4c5f9",2162,"a css problem when running in mobile","2023-01-18T15:43:10Z","https://github.com/nuxt/nuxt/issues/2162",0.7423062,{"description":2050,"labels":2051,"number":2061,"owner":1997,"repository":1997,"state":2033,"title":2062,"updated_at":2063,"url":2064,"score":2065},"### Environment\n\n-\n\n### Reproduction\n\nhttps://nuxt.com/modules/tailwindcss\r\nhttps://nuxt.com/modules/nuxt-viewport\n\n### Describe the bug\n\nUsing the light theme we get code highlighting bug\r\n\u003Cimg width=\"1048\" alt=\"image\" src=\"https://user-images.githubusercontent.com/24970784/202643486-d93875f9-5281-4b09-9ac0-f9c964502058.png\">\r\n\u003Cimg width=\"1046\" alt=\"image\" src=\"https://user-images.githubusercontent.com/24970784/202643580-8d1c222f-3c4c-456a-b00a-a9746e1bd92e.png\">\r\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2052,2055,2058],{"name":2053,"color":2054},"documentation","5319e7",{"name":2056,"color":2057},"3.x","29bc7f",{"name":2059,"color":2060},"pending triage","E99695",15531,"docs: markdown in modules with light theme are broken","2023-01-19T17:53:18Z","https://github.com/nuxt/nuxt/issues/15531",0.76562,{"description":2067,"labels":2068,"number":2011,"owner":1997,"repository":2032,"state":2033,"title":2071,"updated_at":2072,"url":2073,"score":2016},"",[2069],{"name":1985,"color":2070},"ff281a","[footer] fix footer in responsive","2022-12-07T06:20:08Z","https://github.com/nuxt/nuxt.com/issues/989",{"description":2075,"labels":2076,"number":2078,"owner":1997,"repository":1997,"state":2033,"title":2079,"updated_at":2080,"url":2081,"score":2082},"How would be switch to pages for mobile and desktop?\n\n\u003C!--cmty-->\u003C!--cmty_prevent_hook-->\n\u003Cdiv align=\"right\">\u003Csub>\u003Cem>This question is available on \u003Ca href=\"https://nuxtjs.cmty.io\">Nuxt.js\u003C/a> community (\u003Ca href=\"https://nuxtjs.cmty.io/nuxt/nuxt.js/issues/c154\">#c154\u003C/a>)\u003C/em>\u003C/sub>\u003C/div>",[2077],{"name":2042,"color":2043},182,"Mobile based pages","2023-01-18T15:38:32Z","https://github.com/nuxt/nuxt/issues/182",0.76593363,{"description":2084,"labels":2085,"number":2090,"owner":1997,"repository":1998,"state":2033,"title":2091,"updated_at":2092,"url":2093,"score":2094},"### Description\n\nThe Nuxt UI v2 dropdown has the option to open on hover or click. In v3 the only option available is click. \n\n\n\n### Additional context\n\n_No response_",[2086,2089],{"name":2087,"color":2088},"enhancement","a2eeef",{"name":1988,"color":1989},3322,"[DropdownMenu] (v3) missing mode prop for hover/click","2025-03-08T12:22:25Z","https://github.com/nuxt/ui/issues/3322",0.7671338,{"description":2096,"labels":2097,"number":2101,"owner":1997,"repository":1998,"state":2033,"title":2102,"updated_at":2103,"url":2104,"score":2105},"### 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```",[2098,2099,2100],{"name":1985,"color":1986},{"name":1988,"color":1989},{"name":1994,"color":1995},3644,"\u003CUInput> template ref does not work","2025-03-21T13:14:18Z","https://github.com/nuxt/ui/issues/3644",0.7695242,["Reactive",2107],{},["Set"],["ShallowReactive",2110],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"KJsQA4YM7dsPyEaYkEHlhF2o7Glyy_diYtujFjdITTI":-1},"/nuxt/nuxt.com/1057"]