Pages Router: `<Link>` `onClick` / `preventDefault()` semantics broken in new-link-behavior mode
#1,470 建立於 2026年5月22日
倉庫指標
- 星標
- (8,563 顆星)
- PR 合併指標
- (平均合併 1天 1小時) (30 天內合併 462 個 PR)
描述
This issue was created by an agent analysing CI failures from the Next.js Deploy Suite (vinext
mainvs Next.jsv16.2.6, 2026-05-22).
Problem
The Pages Router <Link> shim does not correctly invoke onClick handlers and does not honor event.preventDefault() when running in new-link-behavior mode. Clicks on a Link with an onClick prop do not fire the user's handler, and preventDefault() inside it does not block the resulting navigation.
onClick prop not fired on Link click; preventDefault() does not block navigation
Estimated Impact
~2 test failures across the deploy suite.
Affected Test Suites
test/e2e/new-link-behavior/index.test.ts(2 failures)
Recommendation
-
Reproduce first in vinext's own test suite. Add a
<Link onClick={(e) => { e.preventDefault(); spy(); }} href="/x">test and assertspyran and the address bar did not change. -
Match Next.js click-handler semantics. Invoke
onClickfirst, checkevent.defaultPrevented, and only callrouter.push()if the click is not prevented.