Repository navigation
Conversation
From 1.64, an action whose navigation ends in the redirect's 204 never settles.
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
This was referenced Oct 10, 2026
Racing it let a `goto()` to the same url start before the previous one settled, which fails with `net::ERR_ABORTED`.
Contributor
|
Works for me. good work @kbond |
Contributor
|
i am not shure but eventually this is releated microsoft/playwright#43242 see playwright 1.64.1 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
From Playwright 1.64, an action whose navigation ends in a 204 never settles.
redirectNavigationRequest()answers the navigation with a 204, so a click, form submit, reload, back or forward that hits a redirect hangs until the JSON-RPC timeout.followNavigationRedirects()now stops waiting on such an action once the redirect's 204 has been sent, and navigates to the target as before. Agoto()still settles on the 204 and is still awaited, which includes each redirect hop: starting agoto()to the same URL before the previous one settles fails withnet::ERR_ABORTED.The existing redirect tests cover this when run against 1.64; this adds one for form submissions.