Warning: This build has drifted.
The coverage report for this pull request build may be inaccurate because its base commit is no longer the HEAD of its target branch.
This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

    • Learn more: For more information on this, see Tracking coverage changes for pull request builds.
    • Fix now: For a quick fix, rebase this PR at GitHub. Your next report should be accurate.
    • Prevent going forward: To avoid this issue with future PRs, see these Recommended CI Configurations.

test: fix flaky TestPageCloseRace deadlock

TestPageCloseRace intermittently hung for the full 15m test timeout on CI (reproducible locally ~1 in 8 runs when run alongside TestBrowserContextCloseRace).

Protocol tracing showed page.Close() sends "close" but the Chromium driver never replies when Close() races a navigation that commits at the same instant — a driver-level deadlock outside the binding's control. In the passing case Close() aborts the in-flight navigation (net::ERR_ABORTED) and returns immediately.

Abort the request instead of fulfilling it so the navigation never commits. This still exercises the close-vs-route-handler data race the test guards against (issue #566): the handler goroutine runs concurrently with Close() and reads pageImpl.closeWasCalled, still caught by -race. Verified 30/30 passing with -race after the change.