\r\n```\r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n### Logs\r\n\r\n_No response_",[2964,2965],{"name":2954,"color":2955},{"name":2966,"color":2967},"pages","00DFB5",26034,"closed","scroll jump & visibility issue with page transitions","2025-04-02T08:45:05Z","https://github.com/nuxt/nuxt/issues/26034",0.68991566,{"description":2975,"labels":2976,"number":2981,"owner":2912,"repository":2912,"state":2969,"title":2982,"updated_at":2983,"url":2984,"score":2985},"### Environment\r\n\r\n- Operating System: `Darwin`\r\n- Node Version: `v18.18.2`\r\n- Nuxt Version: `3.6.1`\r\n- Nitro Version: `2.5.2`\r\n- Package Manager: `npm@9.8.1`\r\n- Builder: `vite`\r\n- User Config: `ssr`, `nitro`, `app`, `modules`, `security`, `vite`\r\n- Runtime Modules: `nuxt-security@1.0.0-rc.2`, `nuxt-vitest@0.10.2`\r\n- Build Modules: `-`\r\n\r\n\r\nAlthough we are pinned at Nuxt v3.6.1 'for reasons' the bug can be observed in StackBlitz repro on Nuxt v3.8.2\r\n\r\n### Reproduction\r\n\r\nhttps://stackblitz.com/edit/github-6rrfcj?file=pages%2Findex.vue\r\n\r\nNote: Issue relates to keyboard navigation! - not mouse.\r\n\r\n- Open `index` page and tab bring focus to button labelled `Goto Two`. \r\n- Hit enter key to effectively `click` button. (remember, keyboard - not mouse!)\r\n- Browser navigates to page `two`\r\n\r\nNotice the header suggests that the function `handleNext` has been called. This suggest that the `@keyup` event has fired on the `input` control on page `two` as `handleNext` is the function handling of that event. I can't think why this should be expected behaviour. Almost as if the `keyup` event from pressing the button on the `index` page is being seen by page `two` when the `focus()` call is made?! \r\n\r\nOpen the browser devtools to see console.log messages also indicating that `handleNext` has been called.\r\n\r\nAlso, to add additional context/relevant to help diagnose the error. In the script for `two.vue` there is another option (2) that can be uncommented and option (1) commented out. This only calls `focus()` after a delay. With this in place the potential bug doesn't happen.\r\n\r\n### Describe the bug\r\n\r\nI'm seeing what I think maybe a bug when navigating to a page that combines and `input` control with an associated `@keyup` handler that is also focused on page load via `onMounted` lifecycle event.\r\n\r\nFollow the reproduction above and also the effect of delaying the call to `focus()` on the `input` control.\r\n\r\n\r\n### Additional context\r\n\r\nChanging the event type on the `input` field from `@keyup` to `@keydown` also avoids the issue.\r\n\r\n### Logs\r\n\r\n_No response_",[2977,2980],{"name":2978,"color":2979},"3.x","29bc7f",{"name":2954,"color":2955},24434,"Unexpected @keyup triggering on focused input field when navigated to via keyboard \"click\"","2023-11-28T14:35:12Z","https://github.com/nuxt/nuxt/issues/24434",0.6926697,{"description":2987,"labels":2988,"number":2994,"owner":2912,"repository":2913,"state":2969,"title":2995,"updated_at":2996,"url":2997,"score":2998},"### Environment\n\n- Operating System: `Darwin`\n- Node Version: `v22.14.0`\n- Nuxt Version: `3.17.5`\n- CLI Version: `3.25.1`\n- Nitro Version: `2.11.12`\n- Package Manager: `pnpm@10.11.1`\n- Builder: `-`\n- User Config: `ssr`, `devtools`, `modules`, `css`, `app`, `runtimeConfig`, `i18n`, `icon`, `devServer`, `colorMode`, `compatibilityDate`, `future`, `typescript`, `vite`\n- Runtime Modules: `@nuxt/ui@3.0.1`, `@pinia/nuxt@0.5.5`, `@nuxt/eslint@0.5.7`, `@nuxtjs/i18n@9.5.5`, `@nuxtjs/device@3.2.4`, `@nuxt/image@1.10.0`\n- Build Modules: `-`\n\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.1.1\n\n### Reproduction\n\nhttps://codesandbox.io/p/devbox/nuxt-ui3-n3sxks\n\n### Description\n\nWhen using `USwitch` inside `UTooltip` switch toggle just disappears. You can check reproduction link.\n```vue\n\u003CUTooltip text=\"Just a tooltip\">\n \u003CUSwitch label=\"Just a switch\" />\n\u003C/UTooltip>\n```\n\n\u003Cimg width=\"127\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/5dbcfef5-a4c4-4ec4-b2f3-611212f75c68\" />\n\n### Additional context\n\nWrapping `USwitch` to `div` for example solves issue\n```vue\n \u003CUTooltip text=\"Just a tooltip\">\n \u003Cdiv>\n \u003CUSwitch label=\"'Hackish'\" />\n \u003C/div>\n \u003C/UTooltip>\n```\n\n### Logs\n\n```shell-script\n\n```",[2989,2990,2993],{"name":2903,"color":2904},{"name":2991,"color":2992},"duplicate","cfd3d7",{"name":2906,"color":2907},4333,"USwitch not working inside UTooltip","2025-06-12T13:42:09Z","https://github.com/nuxt/ui/issues/4333",0.6965266,{"description":3000,"labels":3001,"number":3004,"owner":2912,"repository":2912,"state":2969,"title":3005,"updated_at":3006,"url":3007,"score":3008},"### Environment\n\n- Operating System: Darwin\r\n- Node Version: v16.15.0\r\n- Nuxt Version: 3.4.3\r\n- Nitro Version: 2.4.1\r\n- Package Manager: pnpm@8.5.1\r\n- Builder: vite\r\n- User Config: app, devServer, build, vite, vue, modules, image, css, components, i18n, pinia, imports, routeRules, appConfig\r\n- Runtime Modules: @nuxtjs/i18n@8.0.0-beta.11, @unocss/nuxt@0.51.13, @pinia/nuxt@0.4.11, @nuxt/image-edge@1.0.0-28059208.2abef1b, @nuxt/content@2.6.0\r\n- Build Modules: -\n\n### Reproduction\n\nThe Nuxt official website can reproduce this BUG\n\n### Describe the bug\n\nHere is the screen record:\r\n\r\n\r\nAfter I clicked the \"Try it now\" button, the content on the page flashed suddenly, which looks like it scrolled to the top\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[3002,3003],{"name":2978,"color":2979},{"name":2954,"color":2955},21502,"Page \"scroll to top\" when navigating to next route","2023-10-22T08:55:29Z","https://github.com/nuxt/nuxt/issues/21502",0.7027692,{"description":3010,"labels":3011,"number":3014,"owner":2912,"repository":2912,"state":2969,"title":3015,"updated_at":3016,"url":3017,"score":3018},"### Environment\r\n\r\n------------------------------\r\n- Operating System: Linux\r\n- Node Version: v18.16.0\r\n- Nuxt Version: 3.6.5\r\n- Nitro Version: 2.5.2\r\n- Package Manager: npm@9.6.7\r\n- Builder: vite\r\n- User Config: modules, alias, typescript\r\n- Runtime Modules: @pinia/nuxt@0.4.11, @nuxtjs/tailwindcss@6.8.0, @nuxtjs/supabase@0.3.8\r\n- Build Modules: -\r\n------------------------------\r\n\r\n### Reproduction\r\n\r\nhttps://stackblitz.com/edit/github-lzr81f?file=pages%2Fapp%2Findex.vue\r\n\r\n### Describe the bug\r\n\r\nUsing @nuxt/devtools causes the page route: /pages/app/index.vue to return code. So by navigating to `/app` - interestingly, navigating to `/app/` has no issue.\r\n\r\nDisabling the plugin resolves the issue (removing it from nuxt config).\r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n### Logs\r\n\r\n_No response_",[3012,3013],{"name":2978,"color":2979},{"name":2954,"color":2955},22395,"Using @nuxt/devtools causes the page route: /pages/app/index.vue to return code","2023-08-01T15:01:05Z","https://github.com/nuxt/nuxt/issues/22395",0.70318794,["Reactive",3020],{},["Set"],["ShallowReactive",3023],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fvFkaW18bWJ-DA5_2U7J99JxXWpKsMmk1-eFgXVORkzA":-1},"/nuxt/ui/4378"]