` component, specifically with the `v-model:open` binding:\n\n* `v-model:collapsed` works great — it properly handles the collapsed/expanded state.\n* But `v-model:open` doesn't seem to behave as expected. When I bind it to a custom `open` state and try to set it to `false` (e.g., using a custom button), the sidebar doesn’t actually close. Then, as soon as I click anywhere else on the page, the `open` value is automatically reset to `true`.\n\nIt feels like something internal is re-opening the sidebar and overriding the bound value.\n\nOther small notes:\n\n* `\u003CUDashboardSidebarToggle />` is hidden on desktop due to `lg:hidden`, which makes sense for mobile setups. But even when made visible, it doesn’t allow fully toggling the sidebar on desktop — the sidebar remains fixed.\n* I also tried changing the `default-size` prop (e.g., to `16rem` / `256px`), and it didn’t apply immediately. It only worked after clearing the site data. I’m guessing this is due to cookies storing the previous value? Maybe it could be possible to sync the cookie automatically when `default-size` changes?\n\nHere’s a minimal reproduction of the issue: [Here](https://codesandbox.io/p/devbox/polished-cookies-lrv5hm?file=%2Fapp%2Fpages%2Findex.vue%3A9%2C23)\n\nLastly, I was wondering if in the future it might be possible to support a prop like `expand-on-hover`, where a collapsed sidebar could temporarily expand on mouse hover — without pushing the rest of the layout. This could allow building more advanced layouts similar to what Supabase uses: a primary sidebar that stays collapsed when a secondary one is open, but can still expand on hover without shifting the content.\n\nThanks again for your amazing work and for considering these ideas! 😊\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3152,3155,3158],{"name":3153,"color":3154},"bug","d73a4a",{"name":3156,"color":3157},"v3","49DCB8",{"name":3159,"color":3160},"triage","ffffff",4599,"ui","DashboardSidebar: v-model:open not working as expected","2025-07-25T16:31:55Z","https://github.com/nuxt/ui/issues/4599",0.7269073,{"description":3168,"labels":3169,"number":3173,"owner":3143,"repository":3162,"state":3174,"title":3175,"updated_at":3176,"url":3177,"score":3178},"### Environment\n\n- Operating System: `Linux`\n- Node Version: `v22.14.0`\n- Nuxt Version: `3.17.3`\n- CLI Version: `3.25.1`\n- Nitro Version: `2.11.12`\n- Package Manager: `bun@1.2.13`\n- Builder: `-`\n- User Config: `future`, `compatibilityDate`, `devtools`, `modules`, `css`, `components`, `i18n`, `icon`, `runtimeConfig`, `app`, `hooks`, `site`, `sitemap`, `pwa`, `fonts`\n- Runtime Modules: `@nuxt/eslint@1.4.0`, `@nuxt/fonts@0.11.4`, `@nuxt/image@1.10.0`, `@nuxt/scripts@0.11.7`, `@nuxt/ui@3.1.2`, `@nuxtjs/i18n@9.5.4`, `@vueuse/nuxt@13.2.0`, `@pinia/nuxt@0.11.0`, `@nuxtjs/sitemap@7.2.10`, `@vite-pwa/nuxt@1.0.1`\n- Build Modules: `-`\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.1.2\n\n### Reproduction\n\nhttps://codesandbox.io/p/devbox/wizardly-shamir-f8924y\n\n### Description\n\nThe `URadioGroup` component's table variant renders borders incorrectly in RTL mode. This appears to be a visual issue specific to RTL layouts. The expected result is that borders should match the appearance of the LTR layout, but they do not.\n\n### Additional context\n\nIn LTR Mode:\n\n\nIn RTL Mode:\n",[3170,3171,3172],{"name":3153,"color":3154},{"name":3156,"color":3157},{"name":3159,"color":3160},4190,"closed","URadioGroup table variant borders display incorrectly in RTL mode","2025-05-22T12:36:45Z","https://github.com/nuxt/ui/issues/4190",0.6962257,{"description":3180,"labels":3181,"number":3192,"owner":3143,"repository":3162,"state":3174,"title":3193,"updated_at":3194,"url":3195,"score":3196},"### Environment\n\n- Operating System: Darwin\n- Node Version: v20.10.0\n- Nuxt Version: 3.15.4\n- CLI Version: 3.22.2\n- Nitro Version: 2.10.4\n- Package Manager: pnpm@9.11.0\n- Builder: -\n- User Config: modules, devtools, css, content, future, compatibilityDate, image, build, routeRules, site, hooks, icon, colorMode, nitro, typescript, eslint\n- Runtime Modules: @nuxt/ui-pro@3.0.0-beta.2, @nuxtjs/seo@2.2.0, @nuxt/content@3.2.2, @nuxt/eslint@1.1.0, @nuxt/image@1.9.0, @vueuse/nuxt@12.7.0, @nuxtjs/html-validator@2.0.0, nuxt-payload-analyzer@0.1.4\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.0.0-beta.2\n\n### Reproduction\n\n-\n\n### Description\n\nI’ve noticed significant performance issues when using `UPageMarquee` with testimonials. The load time is drastically affected, and the overall experience is slow. It seems like the testimonials component is causing major bottlenecks.\n\nhttps://ui3.nuxt.dev/components/page-marquee#testimonials\n\n```\n\u003Cdiv class=\"flex flex-col gap-4 w-full\">\n \u003CUPageMarquee\n pause-on-hover\n :overlay=\"false\"\n :ui=\"{ root: '[--gap:--spacing(4)] [--duration:80s]', content: 'w-auto py-1' }\"\n >\n \u003CUPageCard\n v-for=\"(testimonial, index) in page.testimonials.items\"\n :key=\"index\"\n class=\"break-inside-avoid\"\n variant=\"subtle\"\n :description=\"testimonial.quote\"\n :ui=\"{\n description: 'before:content-[open-quote] after:content-[close-quote] line-clamp-3'\n }\"\n class=\"w-64 shrink-0\"\n >\n \u003CULandingTestimonial\n v-bind=\"testimonial\"\n class=\"bg-gray-100/50 dark:bg-gray-800/50\"\n />\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.",[3182,3183,3184,3187,3190],{"name":3153,"color":3154},{"name":3156,"color":3157},{"name":3185,"color":3186},"nuxt/ui-pro","00dc82",{"name":3188,"color":3189},"closed-by-bot","ededed",{"name":3191,"color":3189},"stale",3454,"PageMarquee with testimonials have performance trouble","2025-08-20T02:09:17Z","https://github.com/nuxt/ui/issues/3454",0.7050888,{"description":3198,"labels":3199,"number":3207,"owner":3143,"repository":3143,"state":3174,"title":3208,"updated_at":3209,"url":3210,"score":3211},"### Environment\n\nNuxt project info: 9:02:58 AM\n\n------------------------------\n- Operating System: Linux\n- Node Version: v20.18.0\n- Nuxt Version: 3.13.0\n- CLI Version: 3.15.0\n- Nitro Version: 2.10.4\n- Package Manager: pnpm@9.12.2\n- Builder: -\n- User Config: default\n- Runtime Modules: @nuxtjs/tailwindcss@6.12.2, @nuxtjs/color-mode@3.5.2, @nuxt/icon@1.7.2, @nuxt/image@1.8.1, @nuxtjs/google-fonts@3.2.0, @nuxtjs/i18n@8.5.6, @pinia/nuxt@0.5.5, pinia-plugin-persistedstate/nuxt\n- Build Modules: -\n\n### Reproduction\n\ni am absolutely sure that the issue is obvious\n\n### Describe the bug\n\nWhen using `Nuxt 3.14` with `i18n` , layout rendering breaks unexpectedly in RTL mode or the prefix strategy i am not sure i tested it while working with `en` as default and `ar` with `RTL` as second language with `prefix_except_default` strategy. \n\ni am using a default and auth layouts\nwhen changing the language or the url manually from `http://localhost:3000/login` to `http://localhost:3000/ar/login`\nthe layout falls back to the `default` layout.\n\neverything else works fine with the default layout\n\nDowngrading to `Nuxt 3.13` resolves the issue.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3200,3201,3204],{"name":3140,"color":3141},{"name":3202,"color":3203},"needs reproduction","FBCA04",{"name":3205,"color":3206},"possible regression","B90A42",29875,"Nuxt 3.14 Layout Issue: i18n Integration Causes Layout Fallback","2025-01-25T15:39:26Z","https://github.com/nuxt/nuxt/issues/29875",0.7199019,{"description":3213,"labels":3214,"number":3217,"owner":3143,"repository":3143,"state":3174,"title":3218,"updated_at":3219,"url":3220,"score":3221},"### Environment\n\n------------------------------\r\n- Operating System: Darwin\r\n- Node Version: v18.18.2\r\n- Nuxt Version: 3.13.1\r\n- CLI Version: 3.13.1\r\n- Nitro Version: 2.9.7\r\n- Package Manager: yarn@4.4.1\r\n- Builder: -\r\n- User Config: future, srcDir, dir, components, alias, typescript, devtools, modules, routeRules, tailwindcss, postcss, compatibilityDate\r\n- Runtime Modules: @nuxtjs/tailwindcss@6.12.1, @nuxt/image@1.8.0, @nuxt/eslint@0.5.5, @nuxt/content@2.13.2\r\n- Build Modules: -\r\n------------------------------\n\n### Reproduction\n\nNot working hover events demo: nuxt@3.13.1 + vue@3.5.2\r\nhttps://stackblitz.com/edit/nuxt-vue-3-4-beta-squnun?file=src%2Fpages%2Fhome%2FHomePage.vue,src%2Fshared%2Fui%2Fthumb-carousel%2Fuse-thumb-carousel.ts\r\n\r\nWorking demo: nuxt@3.13.0 + vue@3.4.8\r\nhttps://stackblitz.com/edit/nuxt-vue-3-4-beta-uiqqjl?file=src%2Fpages%2Fhome%2FHomePage.vue,src%2Fshared%2Fui%2Fthumb-carousel%2Fuse-thumb-carousel.ts\r\n\r\nWorking non-nuxt demo: Vite(vike) + vue@3.5.2\r\nhttps://stackblitz.com/edit/dajced?file=pages%2Findex%2F%2BPage.vue,components%2Fthumb-carousel%2Fuse-thumb-carousel.ts\r\n\n\n### Describe the bug\n\n- Open non-working demo\r\n- Wait for the server to start up\r\n- Reload the page (1/twice)\r\n- Hover over the thumbs.\r\n- Navigation should work, but nothing happens, although the carousel itself is initialized\r\n\r\nIn working demos all works fine.\n\n### Additional context\n\nI don't understand what must have been changed in nuxt for my code to stop working.\r\nCan you look at the source code of the `useThumbCarousel` hook that links carousel initialization with expected behavior - maybe there is some part of the code there that causes problems? I'm thinking about watchers or refs.\n\n### Logs\n\n_No response_",[3215,3216],{"name":3140,"color":3141},{"name":3205,"color":3206},28856,"Something broken with latest vue (3.5.2+) and latest nuxt (3.13.1)","2024-09-11T19:49:43Z","https://github.com/nuxt/nuxt/issues/28856",0.72049487,{"description":3223,"labels":3224,"number":3235,"owner":3143,"repository":3143,"state":3174,"title":3236,"updated_at":3237,"url":3238,"score":3239},"### Environment\n\n- Operating System: `Linux`\r\n- Node Version: `v16.17.0`\r\n- Nuxt Version: `3.0.0-rc.8`\r\n- Package Manager: `npm@8.15.0`\r\n- Builder: `vite`\r\n- User Config: `modules`\r\n- Runtime Modules: `@nuxtjs/tailwindcss@5.3.2`\r\n- Build Modules: `-`\n\n### Reproduction\n\n**Repo**\r\nhttps://github.com/rhernandog/nuxt3-transitions-issue\r\n\r\n**Live Sample**\r\nhttps://stackblitz.com/edit/nuxt-starter-d2z5mn\n\n### Describe the bug\n\nAs mentioned in discussion #5717 there is an issue with the appear flag in the using transition, transition group and page transition. In the live sample you'll see that the first load the page doesn't appear. If you navigate you'll see the fade out/in transition between pages working as expected. In the users page you should see an animation for a list of items that never happens, but if you make a change in the file and save it, the animation will happen as expected after the hot reload.\r\n\r\nAs reported in the discussion I can confirm that all these animations work as expected in a Vue3 project.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[3225,3228,3229,3232],{"name":3226,"color":3227},"3.x","29bc7f",{"name":3153,"color":3154},{"name":3230,"color":3231},"upstream","E8A36D",{"name":3233,"color":3234},"upstream-bug","B60205",14715,"Nuxt3 - Transition appear Flag not working","2024-06-17T15:27:02Z","https://github.com/nuxt/nuxt/issues/14715",0.72162586,{"description":3241,"labels":3242,"number":3246,"owner":3143,"repository":3143,"state":3174,"title":3247,"updated_at":3248,"url":3249,"score":3250},"### Environment\n\n- Operating System: `Linux`\n- Node Version: `v20.18.1`\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: `extends`, `compatibilityDate`, `devtools`, `ssr`, `devServer`, `modules`, `runtimeConfig`, `i18n`\n- Runtime Modules: `@vueuse/nuxt@13.0.0`, `@nuxtjs/i18n@9.3.1`, `@pinia/nuxt@0.10.1`, `@nuxtjs/tailwindcss@6.13.2`, `@primevue/nuxt-module@4.3.1`, `@nuxt/fonts@0.11.0`\n- Build Modules: `-`\n\n### Reproduction\n\nhttps://stackblitz.com/edit/github-g35yawsg?file=app.vue\n\n(copied from [the Nuxt docs](https://nuxt.com/docs/getting-started/seo-meta#components))\n\n### Describe the bug\n\nSince the 3.16.0 update, the `\u003CStyle>` component does not render any actual styles in the document head. It did work fine in 3.15.4.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3243,3244],{"name":3153,"color":3154},{"name":3245,"color":3203},"🔨 p3-minor",31332,"Nuxt 3.16.0 - Style components are not rendered","2025-03-13T07:45:17Z","https://github.com/nuxt/nuxt/issues/31332",0.7226833,{"description":3252,"labels":3253,"number":3256,"owner":3143,"repository":3143,"state":3174,"title":3257,"updated_at":3258,"url":3259,"score":3260},"### Environment\r\n\r\n```\r\n------------------------------\r\n- Operating System: Linux\r\n- Node Version: v18.18.0\r\n- Nuxt Version: 3.9.2\r\n- CLI Version: 3.10.0\r\n- Nitro Version: 2.8.1\r\n- Package Manager: npm@10.2.3\r\n- Builder: -\r\n- User Config: devtools, css\r\n- Runtime Modules: -\r\n- Build Modules: -\r\n------------------------------\r\n```\r\n\r\n### Reproduction\r\n\r\nhttps://stackblitz.com/edit/nuxt-starter-19up3f?file=pages%2Findex.vue\r\n\r\n### Describe the bug\r\n\r\nThis issue only occurs in the development mode using `nuxt@3.9.2`.\r\n\r\nUnscoped styles are not working on the server side - there are no `style` or `link rel=\"stylesheet\"` elements in the `head`.\r\n`css` option from the `nuxt.config` doesn't work too. Styles are loaded only on the client side so everything flickers.\r\n\r\nScoped styles are working fine.\r\nIf we build the application everything works fine.\r\n\r\n### Additional context\r\n\r\nMaybe [this](https://github.com/nuxt/nuxt/commit/20e88bb171b34a749f5468238815b022163e262e#diff-db3a4ecfe5a4e5a379ed2f515a315f812ddc26b48ce80dd3f2cada3b75c06c12R369) could be a reason for the issue but I'm not 100% sure.\r\n\r\n### Logs\r\n\r\n_No response_",[3254,3255],{"name":3226,"color":3227},{"name":3140,"color":3141},25258,"(3.9.2) Unscoped styles are not working on the server side - only in development","2024-01-17T14:01:48Z","https://github.com/nuxt/nuxt/issues/25258",0.7234766,{"description":3262,"labels":3263,"number":3270,"owner":3143,"repository":3143,"state":3174,"title":3271,"updated_at":3272,"url":3273,"score":3274},"### Environment\n\n- Operating System: `Darwin`\r\n- Node Version: `v20.10.0`\r\n- Nuxt Version: `3.11.2`\r\n- CLI Version: `3.11.1`\r\n- Nitro Version: `2.9.6`\r\n- Package Manager: `npm@10.2.3`\r\n- Builder: `-`\r\n- User Config: `css`\r\n- Runtime Modules: `-`\r\n- Build Modules: `-`\n\n### Reproduction\n\nhttps://github.com/DallasHoff/nuxt-fouc-example\n\n### Describe the bug\n\nUnder certain conditions, I am seeing a flash of unstyled content in the production build of a site since Nuxt 3.10.0. In the provided reproduction, you can see this by building the site (`npm run build`) and then previewing it (`npm run preview`) and watching as the page loads. The links in the navbar will start out unstyled, in a vertical stack, and then switch to being styled in a row.\r\n\r\nIf you then downgrade the project to Nuxt 3.9.3 with no other changes, the FOUC will not happen. Checking the built HTML of the page, you can see that this version has the CSS of the navbar component inlined, where newer versions of Nuxt do not.\r\n\r\nStrangely, the FOUC also only happens with certain configurations of the components. The FOUC does not happen if:\r\n- The `\u003Cstyle>` tag in `layouts/default.vue` is empty.\r\n- The `\u003Cscript>` tag in `components/app/navbar.vue` does not have `lang=\"ts\"`\r\n\r\n#25806 is similar, but that was resolved as an issue with Vite while this issue happens in production and not development. The issue appears if either `nuxt build` or `nuxt generate` is used to build the site.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[3264,3265,3266,3267],{"name":3226,"color":3227},{"name":3153,"color":3154},{"name":3245,"color":3203},{"name":3268,"color":3269},"inline styles","68AF97",27334,"FOUC in Production since Nuxt 3.10.0","2024-12-03T11:32:03Z","https://github.com/nuxt/nuxt/issues/27334",0.72394544,["Reactive",3276],{},["Set"],["ShallowReactive",3279],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$f7k_z2NThrlaQJR3x-dljwK-DjY2fhVorL0P5AEUFclI":-1},"/nuxt/ui/4813"]