Handle pending connections losing context on frame navigation #426
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.
Details
Similar to what is being proposed in #420, this PR fixes intermittent
Ferrum::TimeoutError
as the driver awaits for requests to be completed.What
It was observed that in some scenarios the driver is not always receiving and associated
Network.loadingFailed
for requests that were in-flight as the main frame navigates. This may be happening with either main frame requests or sub-frame ones.I'm not sure if this is the right approach, but it appears to be working. Basically, it flags requests which are no longer relevant to the current page context as
unknown
which are then assumed to be#finished
.Relates to #420