Replies: 2 comments 4 replies
-
I have the same issue. I noticed that the style tag with the class "monaco-colors" is not being recreated. |
Beta Was this translation helpful? Give feedback.
4 replies
-
Well i opened an issue on the asp.net repo and they give me this useful answer, i'm gonna try it out, but it's not a big deal for me to use forceLoad. dotnet/aspnetcore#57100 (comment) |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I make this as a discussion because i'm not able to reproduce this bug on a sample app, so maybe i'm doing something wrong in the actual project where it happens. I have some screenshots, just in case you might have seen this issue before and have some tips.
When loading the page for the first time, or when doing a full refresh, the editor is fine:
As you may know, Blazor use internal navigation like others SPA framework, so it has a router and you can navigate without refreshing the page. This is done via NavLink or NavigationManager. If I navigate in this way to the page where i have the monaco editor, now it fails to initialize properly, without logging any error in the console:
That weid dot you see on the left seems to be a text-area element, but i don't think it's important is just that the layout is broken.
I already call dispose on the editor before navigation but even without it, it doesn't make a difference.
Sorry for not providing a repro.
Beta Was this translation helpful? Give feedback.
All reactions