position when have a component on bottom of \u003Cslot />\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2960,2961,2964],{"name":2925,"color":2926},{"name":2962,"color":2963},"🔨 p3-minor","FBCA04",{"name":2965,"color":2966},"✨ good reproduction","fbca04",26836,"Transition of page change poisition of components","2024-09-13T17:09:06Z","https://github.com/nuxt/nuxt/issues/26836",0.72264785,{"description":2973,"labels":2974,"number":2983,"owner":2906,"repository":2906,"state":2935,"title":2984,"updated_at":2985,"url":2986,"score":2987},"### Environment\n\n- Operating System: Linux\r\n- Node Version: v16.20.0\r\n- Nuxt Version: 3.7.1\r\n- CLI Version: 3.7.3\r\n- Nitro Version: 2.6.2\r\n- Package Manager: npm@9.4.2\r\n- Builder: -\r\n- User Config: experimental\r\n- Runtime Modules: -\r\n- Build Modules: -\n\n### Reproduction\n\nYou can use my old preproduction from #23051 https://stackblitz.com/edit/github-ydxe3t?file=pages%2Findex.vue\r\n\r\nSee that the scoped style (margin) applies to the component. However, if you update Nuxt to 3.7.3, the style no longer applies, since the data-v attribute was removed. \n\n### Describe the bug\n\nThe issue #23051 was fixed in #23095.\r\n\r\nHowever, this prevented scoped style from being applied to the component. \r\n\n\n### Additional context\n\nSorry for the delayed feedback. As I noted in https://github.com/nuxt/nuxt/pull/23095#issuecomment-1712583276 the removal of data-v attribute entirely lead to styles not being reproduced. I already debugged the issue and I'm going to create a PR with a simple suggested fix.\r\n\r\nThis PR will revert the expected behavior of scoped styles as in 3.7.1 while keeping @huang-julien 's fix for 404 on soft navigation due to different component hash.\n\n### Logs\n\n_No response_",[2975,2978,2979,2980],{"name":2976,"color":2977},"3.x","29bc7f",{"name":2925,"color":2926},{"name":2962,"color":2963},{"name":2981,"color":2982},"server components","839413",23385,"Fix for #23051 broke scoped styles in server components","2023-09-28T07:36:15Z","https://github.com/nuxt/nuxt/issues/23385",0.7248029,{"description":2989,"labels":2990,"number":2998,"owner":2906,"repository":2906,"state":2935,"title":2999,"updated_at":3000,"url":3001,"score":3002},"@danielroe @boogie-ben Pull Request https://github.com/nuxt/nuxt/pull/28083 introduces a bug. \r\n`Number.parseFloat('auto')` ( valid syntax for `getComputedStyle(elem)` padding/margin ) will amount to **NAN**\r\n\r\n### Reproduction\r\nN/A\r\n\r\n_Originally posted by @misurito in https://github.com/nuxt/nuxt/issues/28083#issuecomment-2248868657_\r\n ",[2991,2993,2994,2995],{"name":2992,"color":2966},"good first issue",{"name":2925,"color":2926},{"name":2962,"color":2963},{"name":2996,"color":2997},"possible regression","B90A42",28306,"Scroll behavior Bug introduced wit PR 28083","2024-08-07T11:49:25Z","https://github.com/nuxt/nuxt/issues/28306",0.7297507,{"description":3004,"labels":3005,"number":3009,"owner":2906,"repository":2934,"state":2935,"title":3010,"updated_at":3011,"url":3012,"score":3013},"### 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",[3006,3007,3008],{"name":2925,"color":2926},{"name":2928,"color":2929},{"name":2945,"color":2946},4190,"URadioGroup table variant borders display incorrectly in RTL mode","2025-05-22T12:36:45Z","https://github.com/nuxt/ui/issues/4190",0.73201495,{"description":3015,"labels":3016,"number":3019,"owner":2906,"repository":2906,"state":2935,"title":3020,"updated_at":3021,"url":3022,"score":3023},"### Environment\n\n- Operating System: Linux\r\n- Node Version: v18.18.0\r\n- Nuxt Version: 3.10.1\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, ssr, app, css\r\n- Runtime Modules: -\r\n- Build Modules: -\n\n### Reproduction\n\nhttps://stackblitz.com/edit/nuxt-starter-njpvcp\n\n### Describe the bug\n\nThe following is a very common application layout(also shown in layouts/default.vue in the reproduction link):\r\n```\r\n\u003CHeader />\r\n\u003Cslot /> \u003C!-- References to the page -->\r\n\u003CFooter />\r\n```\r\nWhen we use 'out-in' mode in pageTransition in nuxt.config.ts:\r\n```\r\npageTransition: { name: 'page', mode: 'out-in' }\r\n```\r\nAnd we **CLICK ON THE LINK** . This is what's rendered in the DOM.\r\n```\r\n\u003CHeader />\r\n\u003CFooter />\r\n\u003Cslot /> \u003C!-- References to the page -->\r\n```\r\nAlso when we use the following layout:\r\n```\r\n\u003CHeader />\r\n\u003Cdiv>\r\n \u003Cslot /> \u003C!-- References to the page -->\r\n \u003Cp>More Content\u003C/p>\r\n\u003C/div>\r\n\u003CFooter />\r\n```\r\nThis is the result in the DOM, after the link is clicked:\r\n```\r\n\u003CHeader />\r\n\u003Cdiv>\r\n \u003Cp>More Content\u003C/p>\r\n \u003Cslot /> \u003C!-- References to the page -->\r\n\u003C/div>\r\n\u003CFooter />\r\n```\r\nNuxt v3 it seems that append the slot at the end of the parent element. Which seems a bug to me. Looks like there needs to be a handling in appending the slot in the correct order.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[3017,3018],{"name":2976,"color":2977},{"name":2903,"color":2904},25739,"Slot position gets shifted when using the out-in page transition","2024-02-11T09:36:25Z","https://github.com/nuxt/nuxt/issues/25739",0.7343376,{"description":3025,"labels":3026,"number":3033,"owner":2906,"repository":2906,"state":2935,"title":3034,"updated_at":3035,"url":3036,"score":3037},"### Version\r\n```>= 1.0-rc0```\r\n\r\n### Reproduction links\r\nhttps://glitch.com/edit/#!/nuxt-rc0\r\nhttps://nuxt-rc0.glitch.me/\r\nhttps://nuxt-rc0.glitch.me/about\r\n\r\n### Steps to reproduce\r\nLoad the page above, and start typing into the search field. The input element is set to trigger an update of the query string on keypress.\r\n\r\n### What is expected?\r\nYou should be able to continue typing after the first character, and the query string url should continue updating with what you type. \r\n\r\n### What is actually happening?\r\nAfter every keypress, the form field loses focus and you have to click inside again to be able to type the next character.\r\n\r\nAdditionally, if the typing is done on the about page in the above demo, then it also scrolls to the top of the page after each keypress, despite the custom scroll Behaviour disabling that.\r\n\r\n### Extra Information\r\nI noticed this change in behavior when I upgraded from 1.0.0-alpha.4 to 1.0.0-rc3, but after checking the previous versions it seems to have started in 1.0.0-rc0.\r\n\r\nLinks to a glitch to see a working previous version\r\nhttps://glitch.com/edit/#!/nuxt-alpha4\r\nhttps://nuxt-alpha4.glitch.me/\r\nhttps://nuxt-alpha4.glitch.me/about\r\n\r\nTo rule out changes upstream in vue router causing this, I created a jsfiddle using version 2.7.0 of vue-router (same as nuxt 1.0.0-rc3 uses). The behaviour *does not* exist in that test:\r\nhttps://jsfiddle.net/benosman/octu95ra/\r\n\r\nNote: This issue has been rewritten, hopefully to make it clearer to understand what the problem is.\r\n\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/c1112\">#c1112\u003C/a>)\u003C/em>\u003C/sub>\u003C/div>",[3027,3030],{"name":3028,"color":3029},"question","cc317c",{"name":3031,"color":3032},"2.x","d4c5f9",1255,"Pages are fully re-rendered when just query string changes - focus on active element lost","2023-01-18T15:41:00Z","https://github.com/nuxt/nuxt/issues/1255",0.7346184,["Reactive",3039],{},["Set"],["ShallowReactive",3042],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fRJ6LtAFvx68Eth3KKiGC83XPz0nstrIom2fsQ62cE60":-1},"/nuxt/ui/3367"]