\r\n \u003C/NuxtLayout>\r\n\u003C/template>\r\n```\r\n### /pages/index.vue\r\n```vue\r\n\u003Cscript setup lang=\"ts\">\r\nconst route = useRoute();\r\nconsole.log(route.fullPath);\r\n\u003C/script>\r\n\u003Ctemplate>\r\n \u003Cdiv>\r\n \u003Ch1>Home page\u003C/h1>\r\n \u003CNuxtLink to=\"/about\">About Page\u003C/NuxtLink>\r\n \u003C/div>\r\n\u003C/template>\r\n```\r\n### /pages/about.vue\r\n```vue\r\n\u003Ctemplate>\r\n \u003Cdiv>\r\n \u003Ch1>About page\u003C/h1>\r\n \u003CNuxtLink to=\"/\">Home Page\u003C/NuxtLink>\r\n \u003C/div>\r\n\u003C/template>\r\n```\r\n### /layouts/default.vue\r\n```vue\r\n\u003Cscript setup lang=\"ts\">\r\nconst route = useRoute();\r\nconsole.log(route.fullPath);\r\n\u003C/script>\r\n\u003Ctemplate>\r\n \u003Cmain>\r\n \u003Cslot />\r\n \u003C/main>\r\n\u003C/template>\r\n```\r\n## Steps to reproduce\r\n1. Land on the home page\r\n2. View your console and note the logs produced by `/pages/index.vue` and `/layout/default.vue`\r\n3. Press the NuxtLink to go to the about page\r\n4. Press the NuxtLink on the about page to go back to the home page\r\n5. View your console and note the logs produced by `/pages/index.vue` and `/layout/default.vue`\r\n## Behavior\r\n**Current:**\r\n- When first landing on the home page, the logs of the page and the layout are consistent (both show '/' for the `fullPath`)\r\n- Upon navigating to the about page and return to the home page, the logs are different:\r\n - the page logs correctly: `/`\r\n - the layout logs incorrectly: `/about`\r\n\r\n**Expected:**\r\n- Both the layout and the page should have consistent logs (i.e. retrieve the same value from `useRoute()`)\r\n- The layout should display the correct `fullpath`, even when navigating away and returning using the NuxtLink (i.e. it should have logged '/' instead of '/about/' since we are on the home page)\r\n\r\n### Describe the bug\r\n\r\nWhen calling `useRoute()` inside of a layout, it will retrieve the correct value on the initial load or when refreshing the page. Once navigating away using a NuxtLink, it appears to retrieve an incorrect/old value (possibly due to client-side rendering). Please see the reproduction section for details.\r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n### Logs\r\n\r\n_No response_",[2880],{"name":2868,"color":2869},21340,"useRoute providing incorrect data when used in a layout","2025-02-14T19:34:24Z","https://github.com/nuxt/nuxt/issues/21340",0.7152978,{"description":2887,"labels":2888,"number":2901,"owner":2871,"repository":2902,"state":2903,"title":2904,"updated_at":2905,"url":2906,"score":2907},"### Environment\n\n- Operating System: Darwin\n- Node Version: v22.14.0\n- Nuxt Version: 3.16.2\n- CLI Version: 3.25.0\n- Nitro Version: 2.11.9\n- Package Manager: npm@10.9.2\n- Builder: -\n- User Config: ssr, devtools, modules, css, app, runtimeConfig, i18n, devServer, colorMode, compatibilityDate\n- Runtime Modules: @nuxt/ui@3.0.2, @pinia/nuxt@0.5.5, @nuxt/eslint@0.5.7, @nuxtjs/i18n@9.5.3, @nuxtjs/device@3.2.4\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\n3.0.2\n\n### Reproduction\n\nhttps://codesandbox.io/p/devbox/blazing-currying-smhzvr\nnew: https://codesandbox.io/p/devbox/nuxt-ui3-n3sxks\n\n### Description\n\nI have search input inside UDropdownMenu to search items:\n1. When I focus input then hover items input loosing focus\n2. When I start typing input loosing focus and items are getting focus. You can try in reproduction url.\n3. [Offtop] Also there should be slot for menu iteself \n\n### Additional context\n\nAs I said I'm trying to type \"t\" but not working at all. This should not work this way\n\nhttps://github.com/user-attachments/assets/6c684cdb-1d5d-48c8-a5e5-eacf8507f823\n\n### Logs\n\n```shell-script\n\n```",[2889,2892,2895,2898],{"name":2890,"color":2891},"bug","d73a4a",{"name":2893,"color":2894},"needs reproduction","CB47CF",{"name":2896,"color":2897},"v3","49DCB8",{"name":2899,"color":2900},"closed-by-bot","ededed",4098,"ui","closed","Unable to use search input inside UDropdownMenu","2025-06-03T02:11:42Z","https://github.com/nuxt/ui/issues/4098",0.6933993,{"labels":2909,"number":2914,"owner":2871,"repository":2871,"state":2903,"title":2915,"updated_at":2916,"url":2917,"score":2918},[2910,2913],{"name":2911,"color":2912},"3.x","29bc7f",{"name":2868,"color":2869},14450,"navigateTo and useRouter path change with different layouts doesn't load dom elements in client side mode (no ssr)","2023-01-26T16:25:09Z","https://github.com/nuxt/nuxt/issues/14450",0.6961366,{"description":2920,"labels":2921,"number":2924,"owner":2871,"repository":2871,"state":2903,"title":2925,"updated_at":2926,"url":2927,"score":2928},"### Environment\r\n\r\n- Operating System: `Linux`\r\n- Node Version: `v16.17.0`\r\n- Nuxt Version: `3.0.0-rc.13`\r\n- Nitro Version: `0.6.1`\r\n- Package Manager: `pnpm@7.14.2`\r\n- Builder: `vite`\r\n- User Config: `-`\r\n- Runtime Modules: `-`\r\n- Build Modules: `-`\r\n\r\n### Reproduction\r\n\r\nhttps://stackblitz.com/edit/nuxt-starter-92t5di?file=nuxt.config.ts,app.vue,layouts%2Fdefault.vue,pages%2Findex.vue,layouts%2Fuser.vue,pages%2Fuser%2F[id].vue\r\n\r\nWorkaround is commented out in `user.vue`.\r\n\r\nPlease note that url is NOT refreshing in stackblitz' preview. To recreate the issue again you will need to manually open other page and then the main path again, e.g.:\r\n\r\nhttps://nuxt-starter-92t5di--3000.local-credentialless.webcontainer.io/user/1 \r\nhttps://nuxt-starter-92t5di--3000.local-credentialless.webcontainer.io/\r\n\r\n### Describe the bug\r\n\r\nChanges in layout introduced in nuxt/framework#7940 have broken this feature after release of RC12.\r\n\r\nI've intended to work on PR but I can't solve it. You might find a workaround on user side in repro but here is what I've tried in [line 52](https://github.com/nuxt/framework/blob/main/packages/nuxt/src/app/components/layout.ts#L52) in `app/components/layout.ts`:\r\n1. `useRouterRoute()` and `useRoute()` are empty (hence the bug),\r\n2. adding `useRouter().currentRoute.value` from `#app` prevents the layout from updating to new one (so the workaround cannot be applied here, at least in a way I can think of), \r\n3. using `injectedRoute` always results in page render first then layout render and second page rerender (so reintroduces the bug fixed in nuxt/framework#7940).\r\n\r\nBTW. 3 fixtures introduced in the above PR are failing in all 3 cases in my env due to 10s timeout (besides 1 other case).\r\n\r\nI hope that helps, but I guess we will need to wait for `\u003CSuspense>` to work properly first.\r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n### Logs\r\n\r\n_No response_",[2922,2923],{"name":2911,"color":2912},{"name":2868,"color":2869},15375,"`useRoute()` is now empty in layout context after using `navigateTo`","2023-01-19T17:49:14Z","https://github.com/nuxt/nuxt/issues/15375",0.6993751,{"description":2930,"labels":2931,"number":2934,"owner":2871,"repository":2871,"state":2903,"title":2935,"updated_at":2936,"url":2937,"score":2938},"### Environment\n\n------------------------------\r\n- Operating System: Linux\r\n- Node Version: v18.18.0\r\n- Nuxt Version: 3.7.4\r\n- CLI Version: 3.9.0\r\n- Nitro Version: 2.6.3\r\n- Package Manager: npm@9.4.2\r\n- Builder: -\r\n- User Config: -\r\n- Runtime Modules: -\r\n- Build Modules: -\r\n------------------------------\n\n### Reproduction\n\nhttps://stackblitz.com/edit/github-tmvnrq?file=layouts%2Fdefault.vue\n\n### Describe the bug\n\nInconsistent behavior exists between two versions of `useRoute`. The one imported from `vue-router` functions as expected, while the other from Nuxt causes the component to render twice (mount -> unmount -> then mount again). This behavior leads to a performance penalty, particularly on pages with heavy computation.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2932,2933],{"name":2911,"color":2912},{"name":2868,"color":2869},23488,"Using `useRoute` from auto-import makes the page component render twice.","2023-10-01T19:41:21Z","https://github.com/nuxt/nuxt/issues/23488",0.69969994,{"description":2940,"labels":2941,"number":2948,"owner":2871,"repository":2871,"state":2903,"title":2949,"updated_at":2950,"url":2951,"score":2952},"### Environment\r\n\r\n- Operating System: `Darwin`\r\n- Node Version: `v18.7.0`\r\n- Nuxt Version: `3.0.0-rc.8`\r\n- Package Manager: `yarn@1.22.19`\r\n- Builder: `vite`\r\n- User Config: `modules`, `css`, `colorMode`, `vite`, `app`\r\n- Runtime Modules: `nuxt-windicss@2.5.0`, `@pinia/nuxt@0.3.1`, `@nuxtjs/color-mode@3.1.4`, `@nuxt/image-edge@1.0.0-27657146.da85542`\r\n- Build Modules: `-`\r\n\r\n### Reproduction\r\n\r\nhttps://stackblitz.com/edit/github-izskfd?file=components/Book.vue\r\n\r\n### Describe the bug\r\n\r\nuseRoute(), nuxt default provided function, has previous route information, and not updated on moving page.\r\n\r\nBut using `import { useRoute } from vue-router`, resolve all problems.\r\n\r\nIs there any point I missed?\r\n\r\n### Additional context\r\n\r\nrc.6 doesn't have problems but rc.8 has.\r\n\r\nIt just occurred as soon as updating from rc.6 to rc.8\r\n\r\n### Logs\r\n\r\n_No response_",[2942,2945],{"name":2943,"color":2944},"documentation","5319e7",{"name":2946,"color":2947},"🔨 p3-minor","FBCA04",14595,"auto-imported `useRoute()` from nuxt requires use of `\u003CNuxtPage>`","2025-06-03T13:52:48Z","https://github.com/nuxt/nuxt/issues/14595",0.7002846,{"description":2954,"labels":2955,"number":2958,"owner":2871,"repository":2902,"state":2903,"title":2959,"updated_at":2960,"url":2961,"score":2962},"### Environment\n\n- Operating System: Darwin\n- Node Version: v18.20.6\n- Nuxt Version: 3.15.4\n- CLI Version: 3.21.1\n- Nitro Version: 2.10.4\n- Package Manager: yarn@1.22.22\n- Builder: -\n- User Config: -\n- Runtime Modules: -\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.0.0-alpha.13\n\n### Reproduction\n\nhttps://codesandbox.io/p/devbox/modest-agnesi-drlrh4?file=%2Fapp%2Fpages%2Findex.vue%3A24%2C24\n\n### Description\n\nWhen I close a `UDrawer` that I opened via an action from a `UDropdownMenu`, the style on my \u003Cbody> tag still contains `overflow: hidden` and `user-select: none`, which prevents interaction with the page.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2956,2957],{"name":2890,"color":2891},{"name":2896,"color":2897},3406,"User interaction lock after a Drawer/DropdownMenu","2025-02-27T20:57:27Z","https://github.com/nuxt/ui/issues/3406",0.70454776,{"description":2964,"labels":2965,"number":2967,"owner":2871,"repository":2871,"state":2903,"title":2968,"updated_at":2969,"url":2970,"score":2971},"### Environment\n\n- Operating System: `Darwin`\n- Node Version: `v23.6.0`\n- Nuxt Version: `3.15.4`\n- CLI Version: `3.21.1`\n- Nitro Version: `2.10.4`\n- Package Manager: `npm@11.1.0`\n- Builder: `-`\n- User Config: `devtools`, `app`, `routeRules`, `modules`, `runtimeConfig`, `css`, `build`, `ssr`, `spaLoadingTemplate`, `experimental`, `primevue`, `i18n`, `compatibilityDate`, `turnstile`\n- Runtime Modules: `@nuxtjs/tailwindcss@6.12.1`, `@pinia/nuxt@0.5.1`, `@primevue/nuxt-module@4.1.1`, `@nuxtjs/i18n@8.3.1`, `@nuxt/eslint@0.3.13`, `@nuxtjs/turnstile@0.9.10`, `@sentry/nuxt/module@8.55.0`\n- Build Modules: `-`\n\n### Reproduction\n\n[https://stackblitz.com/edit/github-iy4axfop?file=pages%2Fpage2.vue](https://stackblitz.com/edit/github-iy4axfop?file=pages%2Fpage2.vue)\n\n### Describe the bug\n\nWhen doing client-side navigation from one page to another and the second page (the page we are navigating to) is using the useRoute() hook in its setup method. The hook will still contain data from the previous page (path, params, ...). So for example when fetching data in the setup method with useAsyncData will cause issues as the path is not correct and will not contain desired data.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2966],{"name":2890,"color":2891},30977,"useRoute() is containing data from previous page when performing client-side navigation","2025-02-20T15:20:35Z","https://github.com/nuxt/nuxt/issues/30977",0.70811653,{"description":2973,"labels":2974,"number":2980,"owner":2871,"repository":2902,"state":2903,"title":2981,"updated_at":2982,"url":2983,"score":2984},"### Environment\n\nNuxt: 3.15.0\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\n3.0.0-alpha.10\n\n### Reproduction\n\nhttps://codesandbox.io/p/sandbox/lucid-shape-9kk73c\n\n### Description\n\n\nDropdownMenu actions will not work after Udrawer closed.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2975,2976,2977],{"name":2890,"color":2891},{"name":2896,"color":2897},{"name":2978,"color":2979},"triage","ffffff",3067,"UDrawer UDropdownMenu actions conflict","2025-05-23T13:35:59Z","https://github.com/nuxt/ui/issues/3067",0.70856774,["Reactive",2986],{},["Set"],["ShallowReactive",2989],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fjQATzRiVu0PxRTrFHh-WwugtOnbHZjsmh1MQj0I30Jo":-1},"/nuxt/ui/3990"]