This repository has been archived by the owner on May 1, 2024. It is now read-only.
Fix WebView Navigated Status Bug In Android #12169
Merged
Conversation
This file contains 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
On Android, Navigated event args contain wrong status of "Failed" when an asset request receives an error even though the page itself is loaded successfully. Instead, OnReceivedError should check if the request url of the OnReceivedError method is equal to the navigated url. (issue xamarin#11988) This PR fixes the issue by adding the necessary url check.
hartez
approved these changes
Oct 7, 2020
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
On Android, Navigated event args contain wrong status of "Failed" when an asset request receives an error even though the page itself is loaded successfully. Instead, OnReceivedError should check if the request url of the OnReceivedError method is equal to the navigated url. (issue #11988)
This PR fixes the issue by adding the necessary url check.