ListDetailsView: Back/Forward nav buttons are non-operational

[XAML-Knight]

Describe the bug

When interacting with the ListDetailsView in the Sample App, clicking either the Back or Forward buttons (near bottom of list view on left-hand side) does not perform as expected.

Steps to Reproduce

• Can this be reproduced in the Sample App? (Either in a sample as-is or with new XAML pasted in the editor.) If so, please provide custom XAML or steps to reproduce.

No, but the Sample App's ListDetailsView page just happens to be blank.

Steps to reproduce the behavior:

1. Given the following environment (Sample App from main)
2. Go to ListDetailsView
3. Click on either the back or forward button (in the list view, on the left-hand side)

Expected behavior

The selected item in the list view (on left-hand side) will change depending on which direction (back, forwards) was initiated by the user

Screenshots

Environment

Debug, x64

Device form factor:

• Desktop
• Xbox
• Surface Hub
• IoT

Visual Studio

• 2019 Preview (version: 16.10.3),

Hello XAML-Knight, thank you for opening an issue with us!

I have automatically added a "needs triage" label to help get things started. Our team will analyze and investigate the issue, and escalate it to the relevant team if possible. Other community members may also look into the issue and provide feedback 🙌

[michael-hawker]

Thanks @XAML-Knight. These are part of the sample itself, eh? Are they hooked up and not doing anything, or do they just provide no function?

[XAML-Knight]

The ListDetailsView control, itself, serves up an empty CommandBar as a dependency property, and it stays empty, until the Sample page comes along and places two buttons (Back, Forward) in it, with no events/commands wired up.

[michael-hawker]

Yeah, think these were just for design aesthetic vs. meaning to be functional.

We should probably have a comment in the XAML to point out they are placeholders.

We could theoretically create new behaviors for a ListViewBase to move the selected item next or previous and wire those up in the sample via XAML. Not sure how useful those would be, probably a separate issue for us to track and get some community feedback on.