[Bug]: Tree - there is no option to keep an item selected OR expanded and selected at the same time

[vnbaaij]

Component

Other...

Package version

3.0.0-RC.10

@microsoft/fast-element version

2.10.x

Environment

Not applicable

Current Behavior

You can click on an unselected a fluent tree view item to select it. And you can click on a selected fluent tree view item to unselected it. The option to not unselect a selected tree view item is missing. This is the behavior that the tree in Windows File Explorer has.

There is also no way to have an item selected and expanded at the same time.

Configuring an option means that clicking on a selected tree view item doesn't do anything.
See also microsoft/fluentui-blazor#3601

Expected Behavior

It should be possible for a parent tree item to be both selected AND expanded.

Reproduction

https://web-components.fluentui.dev/?path=/docs/components-tree--docs

Steps to reproduce

Click on 'Item 2-1-2' while having the Dev Tools open and watching the element. You can see each click toggles the selected state.

Click on 'Item 1' while having the Dev Tools open and watching the element. You can see it can only be either selected or expanded but not both.

Are you reporting an Accessibility issue?

None

Suggested severity

High - No workaround

Products/sites affected

No response

Are you willing to submit a PR to fix?

no

Validations

• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• The provided reproduction is a minimal reproducible example of the bug.

[marchbox]

Hi @vnbaaij, thanks for reporting this. Is this still reporducable on your end? I can’t reproduce the 2 items you ilsted in "Steps to reproduce" with the current versioin (rc13) here: https://storybooks.fluentui.dev/web-components/?path=/docs/components-tree--docs:

• clicking on "item 2-1-2" doesn’t keep toggling the item’s selected state, it keeps it in selected state
• clicking on "item 1" does initially close the subtree but when it’s clicked again, it does put the item to both selected and expanded states (there could be an argument made that the component should offer a way to separate the actions of toggling the expanded state from selection, but that’d be a design decision first)