Skip to content

Commit 00b901c

Browse files
committed
Updates
1 parent 4482a7a commit 00b901c

File tree

3 files changed

+12
-12
lines changed

3 files changed

+12
-12
lines changed

aspnetcore/blazor/components/lifecycle.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -840,7 +840,7 @@ Create a loading indicator component with a `Loading` parameter that can display
840840
```razor
841841
@if (Loading)
842842
{
843-
<progress id="progress-bar" aria-label="Content loading…"></progress>
843+
<progress id="loadingIndicator" aria-label="Content loading…"></progress>
844844
}
845845
else
846846
{
@@ -868,7 +868,7 @@ If you wish to load styles for the indicator, add them to `<head>` content with
868868
...
869869
</style>
870870
</HeadContent>
871-
<progress id="progress-bar" aria-label="Content loading…"></progress>
871+
<progress id="loadingIndicator" aria-label="Content loading…"></progress>
872872
}
873873
else
874874
{

aspnetcore/blazor/components/rendering.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -326,4 +326,4 @@ The state manager approach is similar to the earlier case with <xref:System.Time
326326
<!-- UPDATE 10.0 Will be removed for a new feature in this area.
327327
Tracked by: https://github.com/dotnet/aspnetcore/issues/49056 -->
328328

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-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>.

aspnetcore/blazor/fundamentals/startup.md

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -592,9 +592,9 @@ app.MapFallbackToFile("index.html", staticFileOptions);
592592

593593
:::moniker range=">= aspnetcore-7.0"
594594

595-
## Client-side loading progress indicators
595+
## Client-side loading indicators
596596

597-
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.
598598

599599
:::moniker-end
600600

@@ -635,7 +635,7 @@ If you wish to load styles for the indicator, add them to `<head>` content with
635635
</style>
636636
</HeadContent>
637637
-->
638-
<progress id="progress-bar" aria-label="Content loading…"></progress>
638+
<progress id="loadingIndicator" aria-label="Content loading…"></progress>
639639
}
640640
else
641641
{
@@ -682,7 +682,7 @@ In a component that adopts Interactive WebAssembly rendering, wrap the component
682682

683683
Create a `ContentLoading` component in the `Layout` folder of the `.Client` app that calls <xref:Microsoft.AspNetCore.Components.RendererInfo.IsInteractive?displayProperty=nameWithType>:
684684

685-
* When `false`, display a loading progress indicator.
685+
* When `false`, display a loading indicator.
686686
* When `true`, render the requested component's content.
687687

688688
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
699699
</style>
700700
</HeadContent>
701701
-->
702-
<progress id="progress-bar" aria-label="Content loading…"></progress>
702+
<progress id="loadingIndicator" aria-label="Content loading…"></progress>
703703
}
704704
else
705705
{
@@ -728,22 +728,22 @@ In `Layout/MainLayout.razor`:
728728

729729
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.
730730

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.
732732

733733
`wwwroot/{ASSEMBLY NAME}.lib.module.js`:
734734

735735
```javascript
736736
export function beforeWebStart(options) {
737737
var progress = document.createElement("progress");
738-
progress.id = 'progressBar';
738+
progress.id = 'loadingIndicator';
739739
progress.ariaLabel = 'Blazor loading…';
740740
progress.style = 'position:absolute;top:50%;left:50%;margin-right:-50%;' +
741741
'transform:translate(-50%,-50%);';
742742
document.body.appendChild(progress);
743743
}
744744

745745
export function afterWebAssemblyStarted(blazor) {
746-
var progress = document.getElementById('progressBar');
746+
var progress = document.getElementById('loadingIndicator');
747747
progress.remove();
748748
}
749749
```
@@ -771,7 +771,7 @@ Replace the `<script>` tag with the following markup that starts Blazor manually
771771
</script>
772772
```
773773

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).
775775

776776
:::moniker-end
777777

0 commit comments

Comments
 (0)