RadzenPanelMenu StaticRendering #1244

Closed
opened 2026-01-29 17:50:57 +00:00 by claunia · 2 comments
Owner

Originally created by @HolyOne on GitHub (May 23, 2024).

I understand that webassembly is not present in static rendering mode.
but the components which are likely to be on the MainLayout such as RadzenPanelMenu,RadzenSwitch should support interaction with javascript so they can be available until webassembly loads.

My scenario here is I have to use microsofts account pages because i need external authentication. And they can only be loaded with static rendering. And I now have to redesign the layout without Radzen components because they wont work on login pages because they have to be static

Originally created by @HolyOne on GitHub (May 23, 2024). I understand that webassembly is not present in static rendering mode. but the components which are likely to be on the MainLayout such as RadzenPanelMenu,RadzenSwitch should support interaction with javascript so they can be available until webassembly loads. My scenario here is I have to use microsofts account pages because i need external authentication. And they can only be loaded with static rendering. And I now have to redesign the layout without Radzen components because they wont work on login pages because they have to be static
Author
Owner

@akorchev commented on GitHub (May 23, 2024):

We don't plan to implement them components with JavaScript as well. We think it defeats the purpose of using Blazor. You should use a pure JS library if you need that.

@akorchev commented on GitHub (May 23, 2024): We don't plan to implement them components with JavaScript as well. We think it defeats the purpose of using Blazor. You should use a pure JS library if you need that.
Author
Owner

@HolyOne commented on GitHub (May 23, 2024):

I accept that but components like RadzenPanelMenu ,RadzenSidebarToggle should be the exception. otherwise it beats the purpose of those components in a blazor webasembly application resulting in a worse user experience on a webassembly auto rendered page because it ends up being rendered staticly.

And visitor tries clicking on that menu like 10 seconds and wonders why its not working.

@HolyOne commented on GitHub (May 23, 2024): I accept that but components like RadzenPanelMenu ,RadzenSidebarToggle should be the exception. otherwise it beats the purpose of those components in a blazor webasembly application resulting in a worse user experience on a webassembly auto rendered page because it ends up being rendered staticly. And visitor tries clicking on that menu like 10 seconds and wonders why its not working.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/radzen-blazor#1244