`Link` Component Sends Unnecessary Quest to Server When Directing to the Anchor in Same Page

[Cierra-Runis]

Link to the code that reproduces this issue

https://codesandbox.io/p/devbox/bold-leakey-ldsc82?workspaceId=ws_Q9uzKhdFBESNeeBCA1zppY

To Reproduce

Notice: CodeSandbox seems doesn't support inspect network status, it's better to reproduce the issue in local.

1. Launch the project
2. Jump between the anchor and inspect the network request

Current vs. Expected behavior

QQ2025512-153752-HD.mp4

Provide environment information

Operating System:
  Platform: win32
  Arch: x64
  Version: Windows 11 Pro
  Available memory (MB): 28525
  Available CPU cores: 16
Binaries:
  Node: 22.15.0
  npm: 10.9.2
  Yarn: N/A
  pnpm: 10.10.0
Relevant Packages:
  next: 15.3.2 // Latest available version is detected (15.3.2).
  eslint-config-next: 15.1.7
  react: 19.1.0
  react-dom: 19.1.0
  typescript: 5.8.3
Next.js Config:
  output: N/A

Which area(s) are affected? (Select all that apply)

Linking and Navigating

Which stage(s) are affected? (Select all that apply)

Other (Deployed)

Additional context

No response

[github-actions]

This closed issue has been automatically locked because it had no new activity for 2 weeks. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.