Windowscommunitytoolkit: MasterDetailsView does not adapt to keyboard control in details view

[twsouthwick]

Keyboard works fine when both master and details are open. However, if only one is open, it automatically shows the details, but it also allows the keyboard to move to new items in the master. This presents a really odd user experience, especially as you can see the outline of the selected item overlaid on the details view.

Here's an example:

[skendrot]

@twsouthwick I'll look at this tonight unless you want to submit a PR for it

[twsouthwick]

I have a very hackly work around in a current project, so I'll see if I can get it cleaned up for a PR

[twsouthwick]

I tried to get this to work in the above PR, but I feel like there are design issues that need to be discussed before it can be correctly fixed.

Here is how the control currently works:

• When in a wide state, the selection in the master list updates the details with touch/keyboard/pointer
• When in a collapsed state, the master list updates the details with touch and pointer; keyboard forces details to update as soon as selection is changed

Challenges in getting this to work:

• [ ] There is no state for narrow and not selected in the storyboarding
• [ ] There is no concept of "clicking" in the control; the details view is directly tied to whatever is selected, which (as seen with the keyboard example) is problematic when distinguishing user intent
• [ ] There is no (easy) extensibility points to be able to manually call an update view method. The current recommendations for extensibility is to extend the XAML by templating or hijacking the SelectedItem event. Both of these are awkward in this case, and definitely not ideal for those (like me) who are not well versed in XAML

[twsouthwick]

Before I spend more time on getting a fix for this, the items I listed above need to be addressed. @skendrot do you have any feedback for the challenges in my previous comment?

[skendrot]

This issue is very similar to #1306. The keyboard needs to allow up/down navigation without selecting an item.
We need to maintain that the ListView in the master section can be restyled to another control, but I think we can make the assumption that the control will be a Selector.

[nmetulev]

Do you think you can make it for 2.1 (code freeze is in one week), or should we push this to 2.2?

[skendrot]

I probably won't be able to get to it for 2.1

[windowstoolkitbot]

This issue seems inactive. Do you need help to complete this issue?

[windowstoolkitbot]

This issue seems inactive. Do you need help to complete this issue?

[windowstoolkitbot]

This issue seems inactive. Do you need help to complete this issue?

[nmetulev]

@skendrot, have you been able to take a look at this for 2.2?

[nmetulev]

Moving issue to 3.0

[windowstoolkitbot]

This issue seems inactive. Do you need help to complete this issue?

[nmetulev]

PR merged