-
Notifications
You must be signed in to change notification settings - Fork 710
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix issue with NavigationView ShoulderNavigation always not behaving correctly #3145
Fix issue with NavigationView ShoulderNavigation always not behaving correctly #3145
Conversation
|
||
if (!IsTopNavigationView() | ||
|| !IsNavigationViewListSingleSelectionFollowsFocus() |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we remove this function altogether? This is more or less a relic now since we are not using ListView anymore and the function doesn't do anything we couldn't do elsewhere (and we already do in a few cases).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It does seem pretty trivial, I think it would probably be easier to parse the code if we removed it
In reply to: 471540013 [](ancestors = 471540013)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
@chingucoding can you merge master to pick up the CI build fix that just went in? |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
Description
The check to determine whether selection should update or not was faulty. Thanks you @pavelshapovalov for pointing that out in your issue!
Motivation and Context
Closes #328
How Has This Been Tested?
Add two new interaction tests.
Since those tests rely on gamepad input, maybe we should disable them right away until we have a more reliable gamepad input logic? (See #2202 for more context).
Screenshots (if appropriate):