position when have a component on bottom of \u003Cslot />\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2050,2053,2056],{"name":2051,"color":2052},"bug","d73a4a",{"name":2054,"color":2055},"🔨 p3-minor","FBCA04",{"name":2057,"color":2058},"✨ good reproduction","fbca04",26836,"Transition of page change poisition of components","2024-09-13T17:09:06Z","https://github.com/nuxt/nuxt/issues/26836",0.7312426,{"description":2065,"labels":2066,"number":2075,"owner":1991,"repository":1991,"state":2031,"title":2076,"updated_at":2077,"url":2078,"score":2079},"### 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_",[2067,2070,2071,2072],{"name":2068,"color":2069},"3.x","29bc7f",{"name":2051,"color":2052},{"name":2054,"color":2055},{"name":2073,"color":2074},"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.73314494,{"description":2081,"labels":2082,"number":2088,"owner":1991,"repository":1991,"state":2031,"title":2089,"updated_at":2090,"url":2091,"score":2092},"### Environment\r\n\r\n[11:42:49] Working directory: /home/projects/qgnimawow.github\r\n[11:42:49] Nuxt project info: \r\n\r\n------------------------------\r\n- Operating System: Linux\r\n- Node Version: v18.18.0\r\n- Nuxt Version: 3.9.0\r\n- CLI Version: 3.10.0\r\n- Nitro Version: 2.8.1\r\n- Package Manager: npm@9.4.2\r\n- Builder: -\r\n- User Config: devtools\r\n- Runtime Modules: -\r\n- Build Modules: -\r\n------------------------------\r\n\r\n### Reproduction\r\n\r\nhttps://stackblitz.com/edit/github-t79jgw?file=app%2Frouter.options.ts\r\n\r\n### Describe the bug\r\n\r\nI'm creating this as a collective ticket tracking various issues that all start in `router.options.ts`. I've spent the last day tracking down and partially fixing those issues (PR will follow shortly). Most of them are small logical issues in the code (checking for the wrong values. wrong timing, ignoring first page load, upstream bug in isChangingPage etc.). Due to time restrictions on my part I can't create separate issues and reproductions for each one of them individually:\r\n\r\n- [x] history back / history forward discards `savedPosition` and overwrites it with `{left: 0, top: 0}`\r\n- [x] hash-link when changing page doesn't get scrolled to\r\n- [x] hash-link is overwritten on first page load / page refresh\r\n- [x] `isChangingPage()` returns a false positive (https://github.com/nuxt/nuxt/issues/24934)\r\n- [x] ~~when navigating to a hash link `scroll-padding-top` is ignored~~\r\n- [x] when refreshing the page (F5) for some reason we get a saved position and the hash in the url is ignored. it should scroll to it however\r\n\r\nI will provide a pull request shortly that imho solve all those navigation issues without regressions or breaking changes.\r\n\r\n### Additional context\r\n\r\nThis is really evident on a site that has a mix of hash-links and non-hash links and relies on browser back button to get to where you came from. Page transitions make it even worse.\r\n\r\n### Logs\r\n\r\n_No response_",[2083,2084,2087],{"name":2051,"color":2052},{"name":2085,"color":2086},"pages","00DFB5",{"name":2054,"color":2055},24941,"Various issues with scroll position on history back / forward, hash-link change, initial load with hash links, etc.","2025-03-27T10:54:26Z","https://github.com/nuxt/nuxt/issues/24941",0.740999,{"description":2094,"labels":2095,"number":2100,"owner":1991,"repository":1991,"state":2031,"title":2101,"updated_at":2102,"url":2103,"score":2104},"### 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>",[2096,2099],{"name":2097,"color":2098},"question","cc317c",{"name":2040,"color":2041},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.74277425,["Reactive",2106],{},["Set"],["ShallowReactive",2109],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"RJ6LtAFvx68Eth3KKiGC83XPz0nstrIom2fsQ62cE60":-1},"/nuxt/ui/3367"]