Support mouse and forward navigation #2164
Merged
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.
Summary of the pull request
References and relevant issues
Addresses #1083, specifically targeting mouse navigation but the fix should apply more broadly to other custom keys.
Similar to #551, this addresses inconsistencies in the invocation of navigation (keyboard accelerator, forward vs. back, mouse, etc.), but does not do anything to address the gap between navigation at the application level (existing navigation service implementation) vs. nested navigation in individual tools, e.g. SetupFlow.
Detailed description of the pull request / Additional comments
Specifically added a keyboard accelerator handler for forward, the existing implementation assumed all accelerator invocations are for back navigation.
PointerPressed is used to identify navigation via XButton1/2 as per https://learn.microsoft.com/en-us/windows/apps/design/basics/navigation-history-and-backwards-navigation#handle-mouse-navigation-buttons, using the page UIElement rather than the defunct CoreWindow in the sample.
Validation steps performed
PR checklist