You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In my blazor server project, i am using blazorise UI library. Using the tab component works just fine in almost all the cases. However controlling the tabs programmatically, in a couple instances the SelectedTabChanged method is invoked twice. First with the actual tab invoked via code secondly on its own with default tab. e-g invoking OnSelectedTabChanged with SecondTab results in selection of FirstTab after second invocation.
What is expected?
SelectedTabChanged to be invoked once
What is actually happening?
SelectedTabChanged gets invoked twice
What browsers do you see the problem on?
No response
Any additional comments?
A similar issue is already reported but says its resolved.
The text was updated successfully, but these errors were encountered:
I believe your problem is that you're manually calling tabsContent.SelectPanel(name); which will result in invoking OnSelectedPanelChanged. Once when Blazor renders the component, once with your code. You don't need to invoke it manually. Just bind the tabs and panels to the same name.
Blazorise Version
1.3.2
What Blazorise provider are you running on?
Bootstrap5
Link to minimal reproduction or a simple code snippet
Steps to reproduce
In my blazor server project, i am using blazorise UI library. Using the tab component works just fine in almost all the cases. However controlling the tabs programmatically, in a couple instances the SelectedTabChanged method is invoked twice. First with the actual tab invoked via code secondly on its own with default tab. e-g invoking OnSelectedTabChanged with SecondTab results in selection of FirstTab after second invocation.
What is expected?
SelectedTabChanged to be invoked once
What is actually happening?
SelectedTabChanged gets invoked twice
What browsers do you see the problem on?
No response
Any additional comments?
A similar issue is already reported but says its resolved.
The text was updated successfully, but these errors were encountered: