This issue was created by an agent analysing CI failures from the Next.js Deploy Suite (vinext main vs Next.js v16.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 assert spy ran and the address bar did not change.
-
Match Next.js click-handler semantics. Invoke onClick first, check event.defaultPrevented, and only call router.push() if the click is not prevented.
Problem
The Pages Router
<Link>shim does not correctly invokeonClickhandlers and does not honorevent.preventDefault()when running in new-link-behavior mode. Clicks on a Link with anonClickprop do not fire the user's handler, andpreventDefault()inside it does not block the resulting 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.