fix: FluentSelect Multiple is always expanded

[mattgoedde]

🐛 Bug Report

When multiple is true, the FluentSelect dropdown is always expanded. This appears to also be the case in the documentation website.

💻 Repro or Code Sample

<FluentSelect TOption="Person"
              Items="@Data.People"
              Id="people-listbox2"
              Multiple="true"
              OptionValue="@(p => p.PersonId.ToString())"
              OptionText="@(p => p.LastName + ", " + p.FirstName)"
              @bind-Value="@SelectedValue"
              @bind-SelectedOptions="@SelectedOptions" />

🤔 Expected Behavior

The dropdown should start closed (open=false) and be open-able and close-able.

😯 Current Behavior

The dropdown is stuck open.

[vnbaaij]

This has always been like that. See for example the v2 version at https://calm-sea-053fa6a03-archivesv2.westeurope.3.azurestaticapps.net/Select#multiple-items

You can also go to https://developer.mozilla.org/en-US/docs/Web/HTML/Element/select and add multiple to the first sample. It will then also show a listbox.

[TuckermanRav]

"This has always been like that" - All that tells me it's been wrong, and has always been wrong. I've never seen a multi-select drop down that doesn't collapse after the user makes their selections. In fact, I'm trying to wrap my head around the logic in even defending the notion. There are zero Microsoft products that behave this way. Not Logic Apps, not Azure Data Studio, not power BI not Azure Portal.

[cornem]

In my opinion, this should be reopened and addressed. The react implementation of Dropdown also supports opening and closing a multi-select component. Here's a screen grab from the Fluent 2 documentation:

[vnbaaij]

I'm hopeful we will get a solution for this with the v3 web components. Until then there is nothing we can do about how the v2 web components are handling his.

Please understand we are completely separate from the React Fluent UI team and are doing this as a side project. Our time and resources are (very) limited.

V2 web components are now in 'archive state' so we will not see any fixes coming to that version anymore as the team is focusing on v3.

"This has always been like that" - All that tells me it's been wrong, and has always been wrong. I've never seen a multi-select drop down that doesn't collapse after the user makes their selections. In fact, I'm trying to wrap my head around the logic in even defending the notion. There are zero Microsoft products that behave this way. Not Logic Apps, not Azure Data Studio, not power BI not Azure Portal.

@TuckermanRav (and others who have raised a thumbs up) we work with what we get from the web components for these Blazor components. The issue lies in the source and we simply can't change that (and do not have the resources to do so). Not defending anything, just stating the facts.

[S1lvan07]

@vnbaaij Is this still beeing worked on, or is it planned to be completed in the future?

Thanks for the response.

[vnbaaij]

Yes, we are still working on that for v5.

In fact, new select component has just been merged in. See https://fluentui-blazor-v5.azurewebsites.net/