\r\n\u003CUNotifications state-key=\"aCustomKey\" :ui=\"{position:'bottom-0 top-auto' }\"/>\r\n```\r\n\r\nAnd then within your app we could call the toast handler we want:\r\n```\r\nRandom.vue\r\nconst toast = useToast(aCustomKey)\r\n```\r\n\r\nLet me know what you think and if you'll be interested on this knowing that i could contribute fully to it.\r\n\r\nThanks!\n\n### Additional context\n\n_No response_",[3244,3245,3248],{"name":3168,"color":3169},{"name":3246,"color":3247},"closed-by-bot","ededed",{"name":3249,"color":3247},"stale",1706,"Allow multiple notifications containers","2025-06-19T02:12:39Z","https://github.com/nuxt/ui/issues/1706",0.7706467,{"labels":3256,"number":3261,"owner":3158,"repository":3158,"state":3201,"title":3262,"updated_at":3263,"url":3264,"score":3265},[3257,3258],{"name":3186,"color":3187},{"name":3259,"color":3260},"2.x","d4c5f9",9566,"app/router.scrollBehavior.js does not work on Android","2023-01-22T15:44:59Z","https://github.com/nuxt/nuxt/issues/9566",0.77254146,{"description":3267,"labels":3268,"number":3271,"owner":3158,"repository":3158,"state":3201,"title":3272,"updated_at":3273,"url":3274,"score":3275},"### 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_",[3269,3270],{"name":3231,"color":3232},{"name":3186,"color":3187},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.77694315,["Reactive",3277],{},["Set"],["ShallowReactive",3280],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fQfqhQ6o45SZPxMccK1Qf5NQBk8wGJo4KfKgNBYd0Bw4":-1},"/nuxt/ui/4104"]