Skip to content

FluentListbox SelectedOptionChanged fire twice with 1st selection #3808

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
ShingYehGit opened this issue May 22, 2025 · 2 comments
Open

FluentListbox SelectedOptionChanged fire twice with 1st selection #3808

ShingYehGit opened this issue May 22, 2025 · 2 comments
Labels
needs: repro code or repository The provided description or code is insufficient to repro the issue

Comments

@ShingYehGit
Copy link

Bug Report

💻 Repro or Code Sample

@foreach (AskList ListAsk in AskLists) { @context.szAsk }

@code {
[Parameter, EditorRequired]
public EventCallback GoToSwitchTab { get; set; }

 List<AskList> AskLists;

async Task OnSelectAskChanged( Ask PickAsk )
{
    if (LastAsk != null && PickAsk == LastAsk)
        return;
    QuerySvc.SelectAsk = PickAsk;
    LastAsk = QuerySvc.SelectAsk;
    GoToSwitchTab.InvokeAsync("SelQueTab");
}

}

🤔 Expected Behavior

SelectedOptionChanged fire twice with 1st selection

SelectedOptionChanged should fire once with an unique selection

😯 Current Behavior

💁 Possible Solution

🔦 Context

🌍 Your Environment

VS 2022 : 17.140
.Net8 Blazor/Wasm FluentUI 4.11.9

  • OS & Device: [e.g. MacOS, iOS, Windows, Linux] on [iPhone 7, PC]
  • Browser [e.g. Microsoft Edge, Google Chrome, Apple Safari, Mozilla FireFox]
  • .NET and Fluent UI Blazor library Version [e.g. 8.0.2 and 4.4.1]
@microsoft-github-policy-service microsoft-github-policy-service bot added the triage New issue. Needs to be looked at label May 22, 2025
@vnbaaij vnbaaij added needs: repro code or repository The provided description or code is insufficient to repro the issue and removed triage New issue. Needs to be looked at labels May 22, 2025
@vnbaaij
Copy link
Collaborator

vnbaaij commented May 22, 2025

Ok, this is the second issue you created without ready to run reproduction code. As mentioned in the first one, we will not be looking at this before it is complete. Standard reply follows. If I were you, I'd focus on getting the reproduction code for your earlier report in place instead of opening another incomplete one...

Please supply us with ready-to-run reproduction code in the form of something we can copy/paste, a (zipped) project structure or a GitHub repository.

We do not have capacity to craft or compose a reproduction for every issue that gets raised.

If no code or repository is provided, this issue will be closed in 3 days

Help us to help you. Thanks.

@ShingYehGit
Copy link
Author

ShingYehGit commented May 25, 2025 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs: repro code or repository The provided description or code is insufficient to repro the issue
Projects
None yet
Development

No branches or pull requests

2 participants