\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.",[2001,2004,2007,2010],{"name":2002,"color":2003},"bug","d73a4a",{"name":2005,"color":2006},"v3","49DCB8",{"name":2008,"color":2009},"pro","5BD3CB",{"name":2011,"color":2012},"triage","ffffff",3454,"PageMarquee with testimonials have performance trouble","2025-03-09T20:39:12Z","https://github.com/nuxt/ui/issues/3454",0.73373,{"description":2019,"labels":2020,"number":2028,"owner":1991,"repository":1992,"state":1993,"title":2029,"updated_at":2030,"url":2031,"score":2032},"We're working on the design of the Nuxt UI v3 documentation. If you're using Nuxt UI and want to be featured on the new website, feel free to comment on this issue with testimonials, showcases of apps or brand logos. It would really help to make Nuxt UI more popular.\n\nThanks a lot!",[2021,2024,2025],{"name":2022,"color":2023},"documentation","0075ca",{"name":2005,"color":2006},{"name":2026,"color":2027},"announcement","ff7a1a",2358,"Showcase","2025-04-02T15:31:34Z","https://github.com/nuxt/ui/issues/2358",0.7485404,{"description":2034,"labels":2035,"number":2039,"owner":1991,"repository":2040,"state":1993,"title":2041,"updated_at":2042,"url":2043,"score":2044},"### Environment\n\n------------------------------\n- Operating System: Linux\n- Node Version: v18.20.3\n- Nuxt Version: 3.16.1\n- CLI Version: 3.23.1\n- Nitro Version: 2.11.7\n- Package Manager: pnpm@8.15.6\n- Builder: -\n- User Config: compatibilityDate, devtools, modules\n- Runtime Modules: @nuxt/test-utils/module@3.17.2\n- Build Modules: -\n------------------------------\n\n### Reproduction\n\nhttps://stackblitz.com/~/github.com/olada/nuxt-starter-enej2mm2\n\n### Describe the bug\n\n## Use Case\n\nUse Case is to write a test for a plugin which provides a custom fetch method.\n\nThe custom fetch (which is pretty much the same as [the one in the \"official\" nuxt recipe](https://nuxt.com/docs/guide/recipes/custom-usefetch)) registers\na response interceptor which redirects to /login using Nuxt's `navigateTo`-method when the api responds with a 401 UNAUTHORIZED status.\n\n## The issue\n\nTo make sure that the functionality works, I want to verify it with a test.\nFor this purpose, I want to use the real `$api` method which is provided by the plugin.\n\nIn the test, I want to be able to verify that the navigation is correctly invoked.\n\nFor that purpose, I want to verify that the navigateTo-mock was invoked with the correct parameters.\n\nHowever, it seems that the mock is not being \"injected\" correctly because I receive following error message from vitest.\n\n```\n ❯ plugins/__tests__/customFetch-with-navigateTo-mock.nuxt.spec.ts (1 test | 1 failed) 13ms\n × Custom Open Fetch with mocked navigateTo > should redirect when fetch not successful and status is 401 12ms\n → expected \"spy\" to be called at least once\n\n⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Failed Tests 1 ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯\n\n FAIL plugins/__tests__/customFetch-with-navigateTo-mock.nuxt.spec.ts > Custom Open Fetch with mocked navigateTo > should redirect when fetch not successful and status is 401\nAssertionError: expected \"spy\" to be called at least once\n ❯ eval plugins/__tests__/customFetch-with-navigateTo-mock.nuxt.spec.ts:35:3\n 33| })).rejects.toThrowError();\n 34| \n 35| expect(navigateToMock).toHaveBeenCalled();\n | ^\n 36| });\n 37| });\n\n⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[1/1]⎯\n\n\n Test Files 1 failed (1)\n Tests 1 failed (1)\n Start at 14:37:37\n Duration 592ms\n```\n\nShould mocking the navigateTo method not be possible in such scenario? Or is it because of that `nuxtApp.runWithContext` which makes this a different story?\n\nShould plugins be tested in a completely different way?\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2036],{"name":2037,"color":2038},"pending triage","5D08F5",1206,"test-utils","Cannot mock navigateTo in test with nuxt environment","2025-03-24T14:18:51Z","https://github.com/nuxt/test-utils/issues/1206",0.7508334,{"description":2046,"labels":2047,"number":2052,"owner":1991,"repository":1992,"state":1993,"title":2053,"updated_at":2054,"url":2055,"score":2056},"### For what version of Nuxt UI are you suggesting this?\n\nv2.x\n\n### Description\n\nIt would be great if there was an option for eager validation if there are errors present on the group.\n\nFor example, when initially filling out the field you don't want eager validation as it's distracting when you aren't finished typing.\n\nHowever if you tab away and there's an error, when fixing the error you'd want immediate feedback with eager-validation.\n\nSo I propose a new prop: `eager-validation-on-error=\"true\"` to improve the UX of forms.\n\nThanks!\n\n### Additional context\n\n_No response_",[2048,2051],{"name":2049,"color":2050},"enhancement","a2eeef",{"name":2005,"color":2006},2599,"FormGroup eager-validation when errors exist","2024-11-22T14:20:31Z","https://github.com/nuxt/ui/issues/2599",0.7683103,{"description":2058,"labels":2059,"number":2063,"owner":1991,"repository":1992,"state":1993,"title":2064,"updated_at":2065,"url":2066,"score":2067},"### Environment\n\n- Operating System: Linux\n- Node Version: v22.14.0\n- Nuxt Version: 3.16.2\n- CLI Version: 3.24.1\n- Nitro Version: 2.11.9\n- Package Manager: yarn@1.22.22\n- Runtime Modules: @nuxt/ui@3.0.2\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.0.2\n\n### Reproduction\n\nDocumentation pinned column example is also displaying this behaviour:\n\n\n### Description\n\nWhen using column pinning, headers and cells containing buttons with icons get their text blurred, but the icon stays as is which makes the pinned text unreadable when icons is on it:\n\n\n\n### Additional context\n\nI have searched what it can be, but did not found any Z index issue, maybe it is linked to svg icons reaction with background. Even with a non transparent background, icon stays on top...\n\n### Logs\n\n```shell-script\n\n```",[2060,2061,2062],{"name":2002,"color":2003},{"name":2005,"color":2006},{"name":2011,"color":2012},3927,"Strange behaviour of buttons icons wrt. background in table columns pinned","2025-04-17T18:43:08Z","https://github.com/nuxt/ui/issues/3927",0.76889133,{"description":2069,"labels":2070,"number":2074,"owner":1991,"repository":1992,"state":1993,"title":2075,"updated_at":2076,"url":2077,"score":2078},"### Environment\n\n------------------------------\n- Operating System: Windows_NT\n- Node Version: v22.13.1\n- Nuxt Version: 3.16.2\n- CLI Version: 3.24.1\n- Nitro Version: 2.11.8\n- Package Manager: yarn@1.22.22\n- Builder: -\n- User Config: compatibilityDate, modules, devtools, experimental, app, css, site, runtimeConfig, build, ui, sourcemap, fonts, future, vite, typescript, eslint, prismic, pwa, sentry \n- Runtime Modules: @nuxt/eslint@1.3.0, @nuxt/ui@3.0.2, @nuxt/image@1.10.0, @nuxtjs/prismic@4.1.0, @nuxtjs/robots@5.2.9, @sentry/nuxt/module@9.12.0, @vite-pwa/nuxt@1.0.0, @vueuse/nuxt@13.1.0, @zadigetvoltaire/nuxt-gtm@0.0.13, nuxt-lodash@2.5.3, @nuxt/scripts@0.11.5\n- Build Modules: -\n------------------------------\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nhttps://pkg.pr.new/@nuxt/ui@3deed4c\n\n### Reproduction\n\nnot working with: \"@nuxt/ui\": \"https://pkg.pr.new/@nuxt/ui@3deed4c\",\n\n\n### Description\n\nSince upgrading i get the following error:\n\nType '(event: FormSubmitEvent\u003CSchema>) => Promise\u003Cvoid>' is not assignable to type '(payload: FormSubmitEvent\u003Cobject>) => void'.\n Types of parameters 'event' and 'payload' are incompatible.\n Type 'FormSubmitEvent\u003Cobject>' is not assignable to type 'FormSubmitEvent\u003C{ email: string; firstName: string; lastName: string; phone: string; terms: boolean; attachmentUri?: string | undefined; comment?: string | undefined; }>'.\n Type 'FormSubmitEvent\u003Cobject>' is not assignable to type '{ data: { email: string; firstName: string; lastName: string; phone: string; terms: boolean; attachmentUri?: string | undefined; comment?: string | undefined; }; }'.\n Types of property 'data' are incompatible.\n Type '{}' is missing the following properties from type '{ email: string; firstName: string; lastName: string; phone: string; terms: boolean; attachmentUri?: string | undefined; comment?: string | undefined; }': email, firstName, lastName, phone, termsts-plugin(2322)\n\n(property) onSubmit?: ((payload: FormSubmitEvent\u003Cobject>) => void) | undefined\n\n\n### Additional context\n\nwas working in 3.0.2\n\n### Logs\n\n```shell-script\n\n```",[2071,2072,2073],{"name":2002,"color":2003},{"name":2005,"color":2006},{"name":2011,"color":2012},3843,"UForm @submit event type error","2025-04-09T15:36:22Z","https://github.com/nuxt/ui/issues/3843",0.78766084,{"description":2080,"labels":2081,"number":2084,"owner":1991,"repository":2085,"state":2086,"title":2087,"updated_at":2088,"url":2089,"score":2090},"https://volta.s3.fr-par.scw.cloud/Clean_Shot_2022_11_16_at_17_20_41_8b14c455c0.mp4\n",[2082],{"name":2002,"color":2083},"ff281a",981,"nuxt.com","closed","[docs]/guide/directory-structure/app.config: missing content + broken nav ","2022-12-07T06:14:48Z","https://github.com/nuxt/nuxt.com/issues/981",0.69997895,{"description":2092,"labels":2093,"number":2096,"owner":1991,"repository":1992,"state":2086,"title":2097,"updated_at":2098,"url":2099,"score":2100},"### Description\n\nHow to enable [IntelliSense](https://ui3.nuxt.dev/components/link#intellisense)\n\nwhen wrie the code on class atribute like this\n `\u003Cdiv class=\"bg-red-500 text-white p-4 flex justify-between\">`\n\n the sugestion not show\n",[2094,2095],{"name":1985,"color":1986},{"name":2005,"color":2006},2949,"VS Code IntelliSense not working","2025-01-06T07:33:40Z","https://github.com/nuxt/ui/issues/2949",0.720337,{"description":2102,"labels":2103,"number":2106,"owner":1991,"repository":1992,"state":2086,"title":2107,"updated_at":2108,"url":2109,"score":2110},"### Environment\n\n------------------------------\n- Operating System: Darwin\n- Node Version: v20.11.1\n- Nuxt Version: 3.14.159\n- CLI Version: 3.15.0\n- Nitro Version: 2.10.4\n- Package Manager: pnpm@9.11.0\n- Builder: -\n- User Config: default\n- Runtime Modules: @nuxt/ui@3.0.0-alpha.8, @nuxtjs/html-validator@1.8.2, @nuxt/image@1.8.1, @nuxt/eslint@0.6.1, @nuxtjs/seo@2.0.0-rc.23\n- Build Modules: -\n------------------------------\n\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\n\"@nuxt/ui\": \"3.0.0-alpha.8\",\n\n### Reproduction\n\n\u003C!-- layouts/default.vue -->\n\u003Ctemplate>\n \u003Cdiv class=\"container mx-auto\">\n \u003Cu-breadcrumb :items=\"items \" />\n \u003Cslot>\u003C/slot>\n \u003C/div>\n\u003C/template>\n\n\n\u003Cscript lang=\"ts\" setup>\nimport { useRoute } from 'vue-router';\n\nconst route = useRoute();\nconst items = useBreadcrumbItems({\n schemaOrg: true,\n});\n\u003C/script>\n\n\n### Description\n\nthis will render the breadcrumbs in a \u003Cdiv> with an aria-label, which is a violation of this rule: https://html-validate.org/rules/aria-label-misuse.html\n\n- Rule ID: aria-label-misuse\n- Category: Accessibility\n- Standards: WCAG 2.2 (A)WCAG 2.1 (A)WCAG 2.0 (A)\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n ERROR HTML validation errors found for /song/justice-genesis-1\n\ninline\n 129:21990 error \"aria-label\" cannot be used on this element aria-label-misuse\n\n✖ 1 problem (1 error, 0 warnings)\n\nMore information:\n https://html-validate.org/rules/aria-label-misuse.html\n\n```",[2104,2105],{"name":2002,"color":2003},{"name":2005,"color":2006},2649,"breadcrumb HTML validation errors","2024-11-15T08:53:33Z","https://github.com/nuxt/ui/issues/2649",0.7304991,["Reactive",2112],{},["Set"],["ShallowReactive",2115],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"UpGKEfBUxAhxTkXWNlPsMF66241OdQ_Di00o6sPBmlc":-1},"/nuxt/nuxt.com/1087"]