\nAnd the rendered link element : \n\u003Cimg width=\"517\" height=\"208\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/fbf26569-fc21-461e-9184-8653d73e53a4\" />\n\n### Logs\n\n```shell-script\n\n```",[3023,3026],{"name":3024,"color":3025},"bug","d73a4a",{"name":3027,"color":3028},"triage","ffffff",4639,"nuxt","ui","open","NuxtUI Pro : PageCard's rendered link \u003Ca> is not accessible with keyboard (tabindex=\"-1\")","2025-08-01T07:51:55Z","https://github.com/nuxt/ui/issues/4639",0.72294843,{"labels":3038,"number":3047,"owner":3030,"repository":3030,"state":3048,"title":3049,"updated_at":3050,"url":3051,"score":3052},[3039,3041,3044],{"name":3040,"color":3028},"stale",{"name":3042,"color":3043},"pending triage","E99695",{"name":3045,"color":3046},"2.x","d4c5f9",7758,"closed","nuxt-link does not pass tabindex attribute to wrapped anchor element","2023-01-22T15:36:04Z","https://github.com/nuxt/nuxt/issues/7758",0.6704088,{"description":3054,"labels":3055,"number":3059,"owner":3030,"repository":3030,"state":3048,"title":3060,"updated_at":3061,"url":3062,"score":3063},"### Environment\n\n- Operating System: Linux\n- Node Version: v20.19.1\n- Nuxt Version: 3.17.5\n- CLI Version: 3.25.1\n- Nitro Version: 2.11.12\n- Package Manager: npm@10.8.2\n- Builder: -\n- User Config: compatibilityDate, devtools\n- Runtime Modules: -\n- Build Modules: -\n\n### Reproduction\n\nhttps://stackblitz.com/edit/github-d1n2dope?file=pages%2Findex.vue\n\nClick a NuxtLink that links to a specific element on another page, like `/example#two`. The section is only scrolled into view when reloading the page.\n\n### Describe the bug\n\nWhen using a link to a specific element, that element is not scrolled into view.\nAdding `external` works, but seems to trigger server-side rendering.\n\n### Additional context\n\nI'm not sure when the problem appeared, but navigating straight to a specific section used to work.\nOur end-to-end tests failed after upgrading from 3.16.0 to 3.17.5, though I could reproduce the error on 3.16.0 in StackBlitz.\n\n### Logs\n\n```shell-script\n\n```",[3056],{"name":3057,"color":3058},"🔨 p3-minor","FBCA04",32366,"NuxtLink with anchor (hash) doesn't jump to element unless defined as external","2025-07-10T13:50:25Z","https://github.com/nuxt/nuxt/issues/32366",0.6799151,{"labels":3065,"number":3069,"owner":3030,"repository":3030,"state":3048,"title":3070,"updated_at":3071,"url":3072,"score":3073},[3066,3067,3068],{"name":3040,"color":3028},{"name":3042,"color":3043},{"name":3045,"color":3046},7541,"Is there the standard, recommended way to make anchor links work properly?","2023-01-22T15:36:01Z","https://github.com/nuxt/nuxt/issues/7541",0.68030417,{"description":3075,"labels":3076,"number":3078,"owner":3030,"repository":3030,"state":3048,"title":3079,"updated_at":3080,"url":3081,"score":3082},"### Environment\n\n- Operating System: `Darwin`\n- Node Version: `v20.19.0`\n- Nuxt Version: `3.17.5`\n- CLI Version: `3.25.1`\n- Nitro Version: `2.11.12`\n- Package Manager: `npm@10.8.2`\n- Builder: `-`\n- User Config: `compatibilityDate`, `devtools`, `router`, `srcDir`, `dir`\n- Runtime Modules: `-`\n- Build Modules: `-`\n\n### Reproduction\n\nhttps://stackblitz.com/~/github.com/yuriystasiv/nuxt-link-hashtag\nhttps://github.com/yuriystasiv/nuxt-link-hashtag\n\n### Describe the bug\n\nAfter updating Nuxt from 3.11.2 to 13.17.5, I noticed that `scrollBehavior: 'smooth'` no longer works correctly when using `NuxtLink` with a hash (#). Navigation to the element still occurs, but instead of a smooth scroll, it jumps immediately to the target and only applies the smooth scroll animation at the very end, which feels abrupt.\n\nThis seems to be caused by NuxtLink now rendering a plain \u003Ca> tag instead of RouterLink. This change happened in [this PR](https://github.com/nuxt/nuxt/pull/30190). When I switch it back to use RouterLink (like in earlier versions), smooth scrolling works correctly again. Here’s a demo with patch:\nhttps://stackblitz.com/~/github.com/yuriystasiv/nuxt-link-hashtag-patch\nhttps://github.com/yuriystasiv/nuxt-link-hashtag-patch\n\n**Expected behavior**\nSmooth scrolling should work with NuxtLink and hash links, even when it’s rendered as an anchor tag.\n\n### Additional context\n\nIs there something that needs to be handled differently in NuxtLink to make smooth scrolling work as expected when using anchor tags?\n\nAs a workaround, you can prevent the default behavior and use navigateTo or router.push manually, like this:\n```\n\u003CNuxtLink\n to=\"#test\"\n @click.prevent=\"navigateToSection('#test')\"\n >example\n\u003C/NuxtLink>\n\u003Cscript setup lang=\"ts\">\nconst route = useRoute();\nconst navigateToSection = (section: string) => {\n navigateTo(`${route.path}${section}`);\n};\n\u003C/script>\n```\n\n### Logs\n\n```shell-script\n\n```",[3077],{"name":3042,"color":3043},32329,"NuxtLink hashtag and scrollBehavior smooth","2025-06-14T13:06:23Z","https://github.com/nuxt/nuxt/issues/32329",0.68951905,{"description":3084,"labels":3085,"number":3087,"owner":3030,"repository":3030,"state":3048,"title":3088,"updated_at":3089,"url":3090,"score":3091},"I'm facing a weird issue on [my website](tchret.com) (powered by nuxt), all the external links are target `_blank`, but don't properly open a new tab \r\n\r\n(Chrome)\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/c2669\">#c2669\u003C/a>)\u003C/em>\u003C/sub>\u003C/div>",[3086],{"name":3045,"color":3046},3083,"target='_blank' disabled on links","2023-01-18T16:09:57Z","https://github.com/nuxt/nuxt/issues/3083",0.7013618,{"description":3093,"labels":3094,"number":3099,"owner":3030,"repository":3030,"state":3048,"title":3100,"updated_at":3101,"url":3102,"score":3103},"### Environment\n\nno\n\n### Reproduction\n\nexample:https://codesandbox.io/p/sandbox/quiet-pine-pwftq4?file=%2Fapp.vue&selection=%5B%7B%22endColumn%22%3A28%2C%22endLineNumber%22%3A30%2C%22startColumn%22%3A28%2C%22startLineNumber%22%3A30%7D%5D\r\n\r\n\n\n### Describe the bug\n\n1. The anchor position cannot be performed normally\r\n2. The anchor position cannot be triggered: the lock of the target pseudo-element\r\n3. Invalid application of scroll-padding-top style\r\n4. The anchor jump between pages cannot be effectively anchored to specify the position in the page\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[3095,3098],{"name":3096,"color":3097},"workaround available","11376d",{"name":3042,"color":3043},20555,"NuxtLink affects the effect of anchor point positioning, which will cause the :target pseudo-element and scroll-padding-top to not work. How to solve it?","2024-09-04T13:38:07Z","https://github.com/nuxt/nuxt/issues/20555",0.7050327,{"description":3105,"labels":3106,"number":3111,"owner":3030,"repository":3030,"state":3048,"title":3112,"updated_at":3113,"url":3114,"score":3115},"### 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>",[3107,3110],{"name":3108,"color":3109},"question","cc317c",{"name":3045,"color":3046},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.71126974,{"description":3117,"labels":3118,"number":3123,"owner":3030,"repository":3030,"state":3048,"title":3124,"updated_at":3125,"url":3126,"score":3127},"### 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_",[3119,3122],{"name":3120,"color":3121},"3.x","29bc7f",{"name":3042,"color":3043},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.7146737,{"description":3129,"labels":3130,"number":3143,"owner":3030,"repository":3030,"state":3048,"title":3144,"updated_at":3145,"url":3146,"score":3147},"### Environment\n\n- Operating System: Windows_NT\n- Node Version: v22.10.0\n- Nuxt Version: 3.14.159\n- CLI Version: 3.15.0\n- Nitro Version: 2.10.4\n- Package Manager: npm@10.9.0\n- Builder: -\n- User Config: default\n- Runtime Modules: @nuxt/eslint@0.6.1\n- Build Modules: -\n\n### Reproduction\n\nhttps://stackblitz.com/edit/github-zxu7oo?file=pages%2Findex.vue\n\n### Describe the bug\n\nWhen `NuxtLink`'s `href` is set to a string starting with `?` or `#`, the `a` tag's rendered `href` value will contain not only that string but also the current route's path prepended to it. This is contrary to the vanilla HTML behavior: `a` tags are allowed to have an `href` value starting with `?` or `#` with no path preceding.\n\nIn both cases, this can break CSS selectors that filter on the `href` attribute. In the case of `#`, prepending the path can break the link since it excludes the query. Simply rendering the `href` the way it was originally set, as expected, would fix this. In fact, when the `href` starts with `#`, it could be rendered as a vanilla `a` tag rather than a router link. No event handler is needed for that.\n\nReproduction steps:\n1. Inspect the \"Query\" link. You'll find `href=\"/?query=1\"`, and its text color is red.\n2. Click the \"Query\" link. The current route changes to `/?query=1`.\n3. Inspect the \"Hash\" link. You'll find `href=\"/#hash\"`, and its text color is red.\n4. Click the \"Hash\" link. The current route changes to `/#hash`.\n\nExpected:\n- All links should be colored blue, not red.\n- Inspecting the \"Query\" link should show `href=\"?query=1\"`, as expected from the source code.\n- Inspecting the \"Hash\" link should show `href=\"#hash\"`, as expected from the source code.\n- Clicking \"Query\" and then \"Hash\" should result in the current route `/?query=1#hash`.\n\n### Additional context\n\nWhen `NuxtLink` is used in `app.vue` instead of in a page, it correctly mirrors the value set in the `href` rather than prepending a path. This issue only affects `NuxtLink`s used in pages.",[3131,3134,3137,3140],{"name":3132,"color":3133},"enhancement","8DEF37",{"name":3135,"color":3136},"good first issue","fbca04",{"name":3138,"color":3139},"pages","00DFB5",{"name":3141,"color":3142},"🍰 p2-nice-to-have","0E8A16",30074,"`NuxtLink` is not drop-in replacement for `\u003Ca href=\"?query\">` or `\u003Ca href=\"#hash\">`","2024-12-31T23:07:57Z","https://github.com/nuxt/nuxt/issues/30074",0.7199834,["Reactive",3149],{},["Set"],["ShallowReactive",3152],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fS4IX5KRCVTkVGumWa8YSmVLtBiMszu1UJ1K3I5AJKHY":-1},"/nuxt/nuxt/9027"]