The demo for blazor component is not working properly. Many time it crashes saying error. (which I can't see). Also the "Source" tab doesn't work. Is it a known issue?
I have tried it with different browsers and on different computers.
The demo for blazor component is not working properly. Many time it crashes saying error. (which I can't see). Also the "Source" tab doesn't work. Is it a known issue?
I have tried it with different browsers and on different computers.
I investigated this a bit more now. I am facing this issue since few weeks. Earlier I had tried with different computers, browsers, incognito modes, etc. and I was convinced that it was a website issue.
What I tried just now was the VPN. When I connect using a VPN the source tab shows normally. (I tried Netherlands location in VPN)
This is the error I get without VPN.
Not sure its my local region specific issue or whole India issue. Would be great if you can try using a VPN with India location and see if you too can reproduce it. My internet provider is JioFiber (biggest in India). I also tried a different provider but got same result. You can give me any domain name or link which I can ping and test if I can connect.
Thanks!
It is not a region specific or website issue since pages open normally at my end(india) without VPN. Try to open the pages on your mobile most probably it might be a LAN/Security/firewall setting issue.
I started getting the error "An error has occurred. This application may no longer respond until reloaded" when clicking on Edit Source in the Demos. This was intermittent with Edge but now happens consistently. However, I do not have a problem when using chrome. When using Edge there are some errors in the console.
It is either caching or you don't have access to the CDN we use to load the Monaco editor JS files:
https://cdnjs.cloudflare.com/ajax/libs/monaco-editor/0.34.1/min/vs/loader.min.js
Thank you for you quick reply. I tried clearing the cache but that did not help. However, I did try again just now, and it is working. I don't know what changed.
But I am no longer getting the error about the CDN. That might have been the problem.