-
Notifications
You must be signed in to change notification settings - Fork 10.7k
Improve Default Blazor WASM Loading Experience #37199
Copy link
Copy link
Closed
Labels
Priority:2Work that is important, but not critical for the releaseWork that is important, but not critical for the releasearea-blazorIncludes: Blazor, Razor ComponentsIncludes: Blazor, Razor Componentscost: MWill take from 3 - 5 days to completeWill take from 3 - 5 days to completeenhancementThis issue represents an ask for new feature or an enhancement to an existing oneThis issue represents an ask for new feature or an enhancement to an existing onefeature-blazor-wasmThis issue is related to and / or impacts Blazor WebAssemblyThis issue is related to and / or impacts Blazor WebAssemblyfeature-templates
Milestone
Metadata
Metadata
Assignees
Labels
Priority:2Work that is important, but not critical for the releaseWork that is important, but not critical for the releasearea-blazorIncludes: Blazor, Razor ComponentsIncludes: Blazor, Razor Componentscost: MWill take from 3 - 5 days to completeWill take from 3 - 5 days to completeenhancementThis issue represents an ask for new feature or an enhancement to an existing oneThis issue represents an ask for new feature or an enhancement to an existing onefeature-blazor-wasmThis issue is related to and / or impacts Blazor WebAssemblyThis issue is related to and / or impacts Blazor WebAssemblyfeature-templates
Type
Fields
Give feedbackNo fields configured for issues without a type.
Currently, when opening a Blazor Wasm app, the user sees
Loading...till everything is downloaded and processed.Ideally, we'd provide an improved loading experience (ex. spinner, loading bar) which is neutrally themed. Users should still be able to easily replace it for their custom applications, but this allows us to provide a great basic alternative.
This loading experience is also the first thing end-users as well as prospective devs for Blazor Wasm would see when trying out a demo app. Consequently, a more visually engaging experience would be ideal.
Accessibility should be a focus with this experience, ensuring screen readers are still able to convey the loading state.
I've seen users express concerns about this across various mediums in the past. Here are a couple of examples (though they're from blog posts providing guidance on how to have custom loading animations).