A nested splitter does not work as expected - the "topmost" splitter does not react to mouse drag/hover events.

[richardv]

This is repeatable in the latest blazor-samples when compiling/running it, but is working fine on the examples page.

The issue appears to be happening when a splitter component is nested. My goal is to use a nested splitter to have a layout such as https://blazor.syncfusion.com/demos/splitter/expand-collapse?theme=bootstrap4 - namely having 2 panes horizontally in which the rightmost pane contains another splitter shich is split horizontally.

Above demo-url is working fine, but when (I suspect due to wasm/serverless blazor mode) I try this in the "run local demos" function in the blazor toolset I am unable to drag the vertical splitter. Only the horizontal (nested) one.

Also, when checkout out chrome-dev I notice an error like:

Uncaught (in promise) Error: System.Text.Json.JsonException: The JSON value could not be converted to blazor_samples.SampleType. Path: $[0].Type | LineNumber: 0 | BytePositionInLine: 1815.

This is my first day using/testing SyncFusion Blazor and I was suspecting I was doing something wrong in my own project when I was attempting to achieve the demo's nested SfSplitter  - But seeing this also repeats in the demo itself I guess asking for support from you guys is my only option :)

Thanks in advance!

[Pandiyaraj Muniyandi]

Hi Richard, 

 

Thanks for your interest in Syncfusion products. 

 

#1: When (I suspect due to wasm/serverless blazor mode) I try this in the "run local demos" function in the blazor toolset I am unable to drag the vertical splitter. Only the horizontal (nested) one. 

 

We validated the reported query and able to reproduce the reported issue from our end. Already we have considered “Nested Splitter layout vertical resizing is not working” as a bug from our end and logged the report for the same and the fix will be included with our patch release on 22^nd  April 2020. 

 

You can now track the current status of the report, review the proposed resolution timeline, and contact us for any further inquiries through this link: https://www.syncfusion.com/feedback/13332/ 

 

#2:  when checkout out chrome-dev I notice an error like: Uncaught (in promise) Error: System.Text.Json.JsonException: The JSON value could not be converted to blazor_samples.SampleType. Path: $[0].Type | LineNumber: 0 | BytePositionInLine: 1815. 

 

This is known application level issue, we have already resolved the issue in the previous releases. Currently, we couldn’t reproduce the above issue with our online demos and github samples from our end. Could you share the following details which help us to address and resolve the issue at earliest. 

• Whether page refresh or component sample navigation scenario this reported issue occurs ?
• Specific NuGet version with github sample have you faced this issue ?

 

Regards, 

Pandiyaraj 

[richardv]

Thanks for your reply! I'il be waiting for the update then.

Regarding your question; I did not download that code from nuget; I simply used the "Syncfusion Blazor Control Panel" and clicked on Explore Demo Source. From there I ran the solution as-is from VS2019 and the issue I mentioned appeared.

It did not appear in the online demo. 

The version of the "Syncfusion Blazor Control Panel" is 18.1.0.42 - 

I consider this issue resolved if this bug is fixed in the 22-4 release and suppose it'd be a waste of (your) time to try and address this from the path I took.

[Rajendran R]

Hi Richard, 

We appreciate that you have taken the time to communicate these details to us. We will resolve the reported issue and ensure it with patch release which is scheduled on April 22, 2020. 

Regards, 

Rajendran R 

[Indrajith Srinivasan]

Hi Richard,

Thanks fro your patience,

We have resolved the issue "Nested Splitter Layout vertical resizing not working" with the SfSplitter and the fix is now available with the Nuget package version 18.1.45.

Sample: https://www.syncfusion.com/downloads/support/forum/153399/ze/Blazor_splitter1254847342

Can you please upgrade you package to this version to resolve the issue from your end?.

Regards, 

Indrajith 

[richardv]

I can confirm this fixed the issue. Thank you!

[Indrajith Srinivasan]

Hi Richard,

Thanks for the update,

We are glad that your reported issue is resoved. Please let us know if you need any further assitance.

Regards, 

Indrajith