fix: two key strokes required to change item in FluentSelect

[majkada]

🐛 Bug Report

While using a FluentSelect with a keyboard 2 key strokes (either arrow up or arrow down) are required to actually change an item.

💻 Repro or Code Sample

E.g. it can be reproduced on https://www.fluentui-blazor.net/Forms with the "Primary Classification" select.

🤔 Expected Behavior

Only one key stroke is required to change an item.

😯 Current Behavior

Exactly two key strokes are required.

• OS & Device: Windows on PC
• Browser Google Chrome
• FluentUI 4.4.0

[vnbaaij]

The strange thing is this only happens in WASM and it is not necessary for every item in a select. Even stranger is that if you add an fluent-select web component, it does work as expected. On Server it works with one keypress regardless.

I'll leave this open, but as the impact is really low and the component works as it should , we won't prioritize finding a solution for it.

[majkada]

I understand.

I looked into it a little and found the issue but I have no idea how to solve it properly.

This line of code executes "too fast"
https://github.com/microsoft/fluentui-blazor/blob/v4.4.0/src/Core/Components/List/ListComponentBase.razor.cs#L534

In WASM the "getAriaActiveDescendant" returns the old item on the first keystroke. You can see it work by just delaying the call even a single millisecond with:

await Task.Delay(TimeSpan.FromMilliseconds(1));

[vnbaaij]

Ok, Adding that delay for the next release 4.4.1.