Splitter not initialising [Collapsed] properly

[Phil Holmes]

As of a few release versions ago, SfSlitter is no longer respecting if [Collapsed] is initialised to true. The splitter pane now opens as NOT collapsed even if the SplitterPane is set to Collapsed=true in the declaration.

The same is true in these 3 cases:

• <SplitterPane Collapsible=true Collapsed=true>
  
• <SplitterPane Collapsible=true Collapsed=@DetailCollapsed>  (where DetailCollapsed=true)
• <SplitterPane Collapsible=true @bind-Collapsed=@DetailCollapsed>

However, if DetailCollapsed is set to false in declaration, then set to true in the component OnInitialized() event, the control does then respond correctly. 

The bug is that it is not accepting the value on declaration. It didn't used to fail this way, but started doing so a month or two ago.

Please advise.

[LeoLavanya Dhanaraj]

Hi Phil,

Greetings from Syncfusion support.

Based on the details you provided, we understand that you are experiencing an issue with the Splitter's Collapsed property. We would like to inform you that both static value assignment and dynamic changes (including value changes and two-way binding) through a button click for the Collapsed property are working properly. For your reference, we have included the validated sample.

Sample : https://blazorplayground.syncfusion.com/LNBSWNhpfvNKZVhO

Refer to the shared sample on your end. Additionally, could you please provide the exact use case scenario for changing the Splitter's Collapsed value inside the OnInitialized Blazor lifecycle method? By sharing your specific scenario, we can investigate and provide a solution.

Regards,

Leo Lavanya Dhanaraj

[Phil Holmes]

Thanks Leo, you are correct. 

Your sample helped me isolate the issue, which was that I had set the non-collapsed pane to Visible-false until data was setup. It seems that when it then became visible, the collapsed states were not as intended.

Anyway, I consider this a problem with my code, not the control, so thanks.

Regards,

Phil

[LeoLavanya Dhanaraj]

Phil, thanks for the update. Please get back to us if you need any further assistance in future.