Port WebBrowser completion events fix from 4.8 #4993
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
ghost
requested review from
ryalanms
approved these changes
Aug 5, 2021
batzen
reviewed
Aug 5, 2021
src/Microsoft.DotNet.Wpf/src/PresentationFramework/MS/Internal/Controls/WebBrowserEvent.cs
Show resolved
Hide resolved
batzen
reviewed
Aug 5, 2021
src/Microsoft.DotNet.Wpf/src/PresentationFramework/MS/Internal/Controls/WebBrowserEvent.cs
Outdated
Show resolved
Hide resolved
ghost
locked as resolved and limited conversation to collaborators
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.
Addresses Issue #4990
Description
When WebBrowser navigates to about:blank, it cancels outstanding navigations. However it may still receive completion events for those navigations, due to race conditions between the browser process and the WPF app. When this happens, ignore the completion event (instead of failing an assert and crashing).
Customer Impact
Intermittent crashes.
Regression
No.
Testing
Ad-hoc around customer scenario.
Standard regressions testing.
Risk
Low. Port of .NETFx servicing fix released earlier this year.