You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description
Blazored Modal problems with the following configuration - Interactive render mode: Auto, Interactivity location: Per page/component in .Net 8
To Reproduce
Create a new project with the following configuration, add Blazored Modal and try to get it working on the client components.
Expected behavior
Blazored Modal working with Blazor Auto rendering mode.
Additional context
If you set interactive mode to Auto where rendering happens on both the server and the client, then the modal is not working. I believe this is due to the fact that the CascadingBlazoredModal is rendered on the server when encapsulating the Routes component. This leaves the client without the CascadingBlazoredModal. I can't find anywhere else where I can wrap the CascadingBlazoredModal to make it cascade to all client components.
I've managed a workaround where I've disabled pre-rendering and moved the Routes component to the client, but this has in effect removed the Auto settings and changed it to WebAssembly.
Is there a way to have this working without moving to WebAssembly only?
The text was updated successfully, but these errors were encountered:
Thanks for raising this @Shique. I believe you are correct. The new render modes have broken a lot of things for people including how this library works.
Right now I believe I need a redesign of the package to make this scenario work.
Description
Blazored Modal problems with the following configuration - Interactive render mode: Auto, Interactivity location: Per page/component in .Net 8
To Reproduce
![image](https://private-user-images.githubusercontent.com/28860696/311241956-87601b7c-22ad-463c-a83a-4af301e86153.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MTkxMDM4MzAsIm5iZiI6MTcxOTEwMzUzMCwicGF0aCI6Ii8yODg2MDY5Ni8zMTEyNDE5NTYtODc2MDFiN2MtMjJhZC00NjNjLWE4M2EtNGFmMzAxZTg2MTUzLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA2MjMlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwNjIzVDAwNDUzMFomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWQxZDUzNjQ5YTNlNzI0M2FjN2U1NGU2YjlkY2Q0YTVmMjlmYWIxMmRiY2ZjZjViMDM2MGIwZmI4NWQ3YzIwOWQmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.qsOhxBZVOsgF90-2GYFky1OLKD7NoumWyGFcalPKFE4)
Create a new project with the following configuration, add Blazored Modal and try to get it working on the client components.
Expected behavior
Blazored Modal working with Blazor
Auto
rendering mode.Additional context
If you set interactive mode to
Auto
where rendering happens on both the server and the client, then the modal is not working. I believe this is due to the fact that theCascadingBlazoredModal
is rendered on the server when encapsulating theRoutes
component. This leaves the client without theCascadingBlazoredModal
. I can't find anywhere else where I can wrap theCascadingBlazoredModal
to make it cascade to all client components.I've managed a workaround where I've disabled pre-rendering and moved the
Routes
component to the client, but this has in effect removed theAuto
settings and changed it toWebAssembly
.Is there a way to have this working without moving to
WebAssembly
only?The text was updated successfully, but these errors were encountered: