Premier Developer Consultant Wael Kdouh explores how to detect unsupported browsers under a Blazor WebAssembly application.

I recently ran into an issue where running a Blazor WebAssembly application under unsupported browsers would simply get stuck on the loading page. Whereas older browsers are supported under the “Server Side” model, it would be a much better experience to present the user with a more meaningful indicator that the browser is not supported when running “Blazor WebAssembly” model. Currently, when running Blazor WebAssembly under older browsers you get a loading indicator that never materializes to a page.

This post chronicles my journey while attempting to uncover a viable solution. The source code is hosted on my Github repository which can be found here. You can test an instance of the running solution which is hosted as a Github page here.

Continue reading on Wael’s blog.