You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A loading progress indicator isn't present in an app created from the Blazor Web App project template. A new loading progress indicator feature is planned for a future release of .NET. In the meantime, an app can adopt custom code to create a loading progress indicator. For more information, see <xref:blazor/fundamentals/startup#client-side-loading-progress-indicators>.
329
+
A loading progress indicator isn't present in an app created from the Blazor Web App project template. A new loading progress indicator feature is planned for a future release of .NET. In the meantime, an app can adopt custom code to create a loading progress indicator. For more information, see <xref:blazor/fundamentals/startup#client-side-loading-indicators>.
A loading progress indicator shows the loading progress of the app to users, indicating that the app is loading normally and that the user should wait until loading is finished.
597
+
A loading indicator shows that the app is loading normally and that the user should wait until loading is finished.
598
598
599
599
:::moniker-end
600
600
@@ -635,7 +635,7 @@ If you wish to load styles for the indicator, add them to `<head>` content with
@@ -682,7 +682,7 @@ In a component that adopts Interactive WebAssembly rendering, wrap the component
682
682
683
683
Create a `ContentLoading` component in the `Layout` folder of the `.Client` app that calls <xref:Microsoft.AspNetCore.Components.RendererInfo.IsInteractive?displayProperty=nameWithType>:
684
684
685
-
* When `false`, display a loading progress indicator.
685
+
* When `false`, display a loading indicator.
686
686
* When `true`, render the requested component's content.
687
687
688
688
If you wish to load styles for the indicator, add them to `<head>` content with the <xref:Microsoft.AspNetCore.Components.Web.HeadContent> component. For more information, see <xref:blazor/components/control-head-content>.
@@ -699,7 +699,7 @@ If you wish to load styles for the indicator, add them to `<head>` content with
@@ -728,22 +728,22 @@ In `Layout/MainLayout.razor`:
728
728
729
729
Add a [JavaScript initializer](#javascript-initializers) to the app. In the following JavaScript module file name example, the `{ASSEMBLY NAME}` placeholder is the assembly name of the server project (for example, `BlazorSample`). The `wwwroot` folder where the module is placed is the `wwwroot` folder in the server-side project, not the `.Client` project.
730
730
731
-
The following example uses a [`progress`](https://developer.mozilla.org/docs/Web/HTML/Element/progress) indicator that doesn't indicate specific progress as [client-side boot resources are delivered to the client](#load-client-side-boot-resources), but it serves as a general approach for further development if you want the progress indicator to show the actual progress.
731
+
The following example uses a [`progress`](https://developer.mozilla.org/docs/Web/HTML/Element/progress) indicator that doesn't indicate specific progress as [client-side boot resources are delivered to the client](#load-client-side-boot-resources), but it serves as a general approach for further development if you want the progress indicator to show the actual progress of loading the app's boot resources.
var progress =document.getElementById('progressBar');
746
+
var progress =document.getElementById('loadingIndicator');
747
747
progress.remove();
748
748
}
749
749
```
@@ -771,7 +771,7 @@ Replace the `<script>` tag with the following markup that starts Blazor manually
771
771
</script>
772
772
```
773
773
774
-
If you notice a short delay between the loading indicator removal and the first page render, you can guarantee removal of the indicator after rendering by calling for indicator removal in the `MainLayout` component's [`OnAfterRenderAsync` lifecycle method](xref:blazor/components/lifecycle#after-component-render-onafterrenderasync). For more information and a code example, see [Document an approach for a loading indicator that works with global Interactive WebAssembly without prerendering (`dotnet/AspNetCore.Docs`#35111)](https://github.com/dotnet/AspNetCore.Docs/issues/35111#issuecomment-2778796998).
774
+
If you notice a short delay between the loading indicator removal and the first page render, you can guarantee removal of the indicator after rendering by calling for indicator removal in the [`OnAfterRenderAsync` lifecycle method](xref:blazor/components/lifecycle#after-component-render-onafterrenderasync) of either the `MainLayout` or `Routes` components. For more information and a code example, see [Document an approach for a loading indicator that works with global Interactive WebAssembly without prerendering (`dotnet/AspNetCore.Docs`#35111)](https://github.com/dotnet/AspNetCore.Docs/issues/35111#issuecomment-2778796998).
0 commit comments