Render Mode InteractiveAuto Problem On Syncfusion Controls.
Hey, I am checking components behaviour on InteractiveAuto mode.
First i will explain with code pictures. downbelow i will share the project.
My interactivity mode is "Per page mode"
Counter.razor;
@page "/counter"
<Blazor.Client.Schedule @rendermode=InteractiveServer></Blazor.Client.Schedule>
<Blazor.Client.Pie @rendermode=InteractiveAuto></ Blazor.Client.Pie >
One is InteractiveServer other is InteractiveAuto mode.
Inside of these compoentns are copy paste from your demos. Uses local datasources.
Pie component has to stop using singnalR after couple forth and back among pages.
But just because there is one more component on the page which using InteractiveServer (Schedule),
Pie components is not swicthing to WASM rendering Still using signalR sonnections. Here how i understand this;
I am checking SignalR messages. Refrehing page couple times. Pie component still works with signalR.
When i change Schedular To Auto mode. Then Both works as it has to be.
Is it by design on sycnfusion?
Hi,
Greetings from Syncfusion Support !
Based on the provided details, we have developed a Blazor Server App targeting .NET 8.0 using "Auto" interactivity render mode, with the interactivity location set to "Per page/component". We included the schedule and pie components as indicated in your code snippet. The behavior of the SignalR connection remaining connected after refreshing the page a couple of times appears to be default framework behavior rather than an issue specific to Syncfusion components.
Additionally, we replicated the sample using default HTML components and observed the same behavior, with the SignalR connection remaining in a connected state after a page reload, as noted below.
Please review the attached sample and response and get back to us if you have any further queries.
Regards,
Subathra K.
Attachment: BlazorAppAutoMode_478c2a63.zip
