-
Notifications
You must be signed in to change notification settings - Fork 98
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Sometimes not initialized correctly #126
Comments
I found a workaround. It seems that if you set your render mode on a per-component basis, the necessary JavaScript script files from Monaco are not loaded properly when establishing a web socket connection or when downloading the DLL in WebAssembly mode. That's why you notice a delay and sometimes a full page reload is needed for the text editor to work. So, in order for it to work, you need to establish a WebSocket connection readily when accessing the page. This can be achieved by setting the render mode globally. In this case, I choose 'InteractiveAuto' and add it to the Routes in the App.razor page.
Finally, I moved all my pages that needs interactivity into the client project, including my layout, and the Routes.razor page. For more info you can check I believe one drawback of this approach is being limited to 'auto' mode, thus unable to utilize Server-Side Rendering (SSR). |
I'm pretty new to Blazor and am not that good at debugging.
I'm running in rendermode
InteractiveServer
(otherwise its not working at all).The text was updated successfully, but these errors were encountered: