Why doesn't Microsoft provide support for older browsers and Blazor WASM
I've built my site using Blazor WASM. I need to provide guidance to our call center when a user calls and asks whether the site works in Chrome version xyz etc.
Microsoft supports the "Current" version.
https://learn.microsoft.com/en-us/aspnet/core/blazor/supported-platforms?view=aspnetcore-7.0
This isn't particularly helpful since we can only advise users - "make sure Chrome is up to date and try again".
Does "Current" mean "Stable Release"? https://en.wikipedia.org/wiki/Google_Chrome_version_history
Is there a reason why Microsoft doesn't support N-1? I noticed Microsoft takes this approach to Azure Portal as well. I'm wondering if this is an industry trend.
https://learn.microsoft.com/en-us/azure/azure-portal/azure-portal-supported-browsers-devices
Blazor wasm is supported by older versions of browsers that supports wasm (Chrome, Firefox, Edge, Opera).
The initial version of wasm for each browser is listed here:
source: https://developer.mozilla.org/en-US/docs/WebAssembly
In theory these versions should support blazor wasm.
That said... Microsoft putting current+ is misleading.
- Blazor WASM styling missing when hosted in docker using nginx
- ASP.NET Core / Blazor: How to implement Permissions based (non-Policy) Authorization
- Blazor using typescript and import three.js
- Register event from blazor component into razor page
- .Net Core - Use AzureAD/EntraID Authentication to Access Azure DevOps REST APIs
- .NET 9 Blazor Hybrid with web app. Accessing WebAssembly DI
- Blazor WASM Deployment Not Including All wwwroot Folders and Files
- Blazor WebAssembly CSS isolation scoped identities doesn't match
- Blazor Web App .NET 8: Line by line debugging is broken. Value cannot be null. Parameter name: source
- .NET 9 Blazor WebAssembly, line by line debugging not working: "The debug adapter exited unexpectedly"
- Capture [SPACE] without jumping in Browser
- Playwright tests fail when using MudDatePicker with mask attribute
- <input type="radio"> not binding with @bind in Blazor WASM in .NET 9
- Microsoft.AspNetCore.Components.Forms.InputDate requires a cascading parameter of type EditContext
- Integrating Blazor Web Assembly into ReactJS
- Can two Blazor WASM clients communicate with each other in local network?
- .NET Core 8 - Download file, client does not have the Content-Disposition Header
- .Net Blazor id The MERGE statement conflicted with the FOREIGN KEY constraint problem
- How to stop Blazor from reloading page and clearing html tag?
- There was no runtime pack for Microsoft.AspNetCore.App available for the specified RuntimeIdentifier 'browser-wasm'
- How to model a target class for receiving a JSON HTML response in .NET 5
- CORS blocks direct access to API from Blazor
- How to create and download an Excel workbook with "Enable Editing" using ClosedXml in a Blazor WASM app
- Why use await Task.Delay(1) in Blazor wasm?
- "dotnet new blazorwasm --hosted" this command fails to work
- InputText : unable to implement CSS for InputText
- FluentUI: Capture KeyCode [Ctrl] + Mouseclick
- How to make my blazor webassembly project run from file folder (by double clicking to open it)
- How can I create a new layout using Blazor Bootstrap?
- Getting access token in Blazor WASM Standalone