[PM-6552] Fix for Android Window issues when opening Autofill/Accessibility #3051
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.
Type of change
Objective
There are still several edge cases in which the app should try to execute the navigation after showing the HomePage and doesn't.
As an alternative we are trying to always try to Navigate when
CreateWindow
is launched on Android.Code changes
Removed several of the Window Workarounds for Android. Now always relying on the
AndroidNavigationRedirectPage
AndroidNavigationRedirectPage
now more resilient to failure and navigates to HomePage as fallback.AndroidNavigationRedirectPage
AutofillWindow
andMainWindow
is no longer needed as we don't reuse or differentiate anymoreBefore you submit
dotnet format --verify-no-changes
) (required)