Unexpected Behavior with FluentTabs and FluentTab Components

[jadAzar12]

what about the case where OnParametersSetAsync is triggered in the child component whenever a property of the bound EditContext is changed ?This behavior happens even when no parameters have changed. This only happens if the parent component is handling an event callback from the child.if the parent does not handle any event callback from the child, it works as expected.

Originally posted by @jadAzar12 in #3652 (reply in thread)

[vnbaaij]

If the parent handles an event callback (regardless of where it is originating from), it is standard Blazor behavior that the child components will re-render and so OnParameterSetAsync will be called.

[jadAzar12]

But why when the child component is placed outside the FluentTabs and FluentTab in the parent component it works as expected , the issue occurs when the child is declared inside the fluentTab , like the bellow

<FluentTab Label="Tab two" Id="tab-2" DeferredLoading="@DeferredLoading">
     <LoadingContent>
         <FluentProgressRing />
     </LoadingContent>
     <Content>
         <ChildComponent OnSubmitFinished="@HandleSubmit"></ChildComponent>
        @*  <ChildComponent></ChildComponent> *@
         Tab two content. This is for testing.
     </Content>
 </FluentTab>

[vnbaaij]

1. Do not just open new issues. Even i the issue is close, we still get notified on (and respond to) new comments
2. Format your code, please. You need to use three ` to get a code block
3. I don not understand what you mean with this code and 'placed outside'. If a component is not inside the FluentTab, it is not a child component and will not get triggered to re-render.

I still don't think this is an issue, so I'm converting it into a discussion.

[jadAzar12]

you can find the solution here : https://github.com/jadAzar12/BlazorAppTest.git

From the sidebar, navigate to the ParentComponent. Inside, you'll find a tab component with three tabs.
1 -Go to the second tab.
2-Modify the value of the input field.
3-Click anywhere outside the input field.

At this point, you'll observe that the OnParametersSetAsync method of the child component is triggered. This behavior only occurs when the child component is inside the tab component.

However, if you move the child component outside the tab component, everything behaves as expected OnParametersSetAsync is not triggered on input blur.

You can verify this behavior by checking the console logs in the browser’s Developer Tools.