Merge branch 'main' into 10/metrics/1

Author: Rick-Anderson

.github/ISSUE_TEMPLATE/doc-request.md

@@ -5,12 +5,12 @@ about: Request a new topic to help us improve
 
 **Help us make content visible**
 
-- Tell us what search terms you used and how you searched docs.
-- Tell us what docs you found that didn't address your concern.
+* Tell us what search terms you used and how you searched docs.
+* Tell us what docs you found that didn't address your concern.
 
 **Describe the new topic**
 
-- Explain why this topic is needed.
-- Suggest a location in the Table of Contents.
-- Write an abstract. In one **short** paragraph, describe what this topic will cover.
-- Create an outline for the new topic. We'll help review the outline and approve it before anyone writes a topic.
+* Explain why this topic is needed.
+* Suggest a location in the Table of Contents.
+* Write an abstract. In one **short** paragraph, describe what this topic will cover.
+* Create an outline for the new topic. We'll help review the outline and approve it before anyone writes a topic.

.openpublishing.redirection.json

@@ -1387,6 +1387,16 @@
             "source_path": "aspnetcore/blazor/host-and-deploy/server.md",
             "redirect_url": "/aspnet/core/blazor/host-and-deploy/server/",
             "redirect_document_id": false
+        },
+        {
+            "source_path": "aspnetcore/blazor/host-and-deploy/webassembly/runtime-and-app-bundle-caching.md",
+            "redirect_url": "/aspnet/core/blazor/host-and-deploy/webassembly/bundle-caching-and-integrity-check-failures",
+            "redirect_document_id": false
+        },
+        {
+            "source_path": "aspnetcore/blazor/host-and-deploy/webassembly/integrity-check-failures.md",
+            "redirect_url": "/aspnet/core/blazor/host-and-deploy/webassembly/bundle-caching-and-integrity-check-failures",
+            "redirect_document_id": false
         }
     ]
 }

aspnetcore/blazor/components/index.md

@@ -1071,14 +1071,14 @@ For more information, see <xref:mvc/views/razor>.
 > [!WARNING]
 > Providing initial values for component parameters is supported, but don't create a component that writes to its own parameters after the component is rendered for the first time. For more information, see <xref:blazor/components/overwriting-parameters>.
 
-Component parameters should be declared as *auto-properties*, meaning that they shouldn't contain custom logic in their `get` or `set` accessors. For example, the following `StartData` property is an auto-property:
+Component parameters should be declared as [automatically-implemented properties (*auto properties*)](/dotnet/csharp/programming-guide/classes-and-structs/auto-implemented-properties), meaning that they shouldn't contain custom logic in their `get` or `set` accessors. For example, the following `StartData` property is an auto property:
 
 ```csharp
 [Parameter]
 public DateTime StartData { get; set; }
 ```
 
-Don't place custom logic in the `get` or `set` accessor because component parameters are purely intended for use as a channel for a parent component to flow information to a child component. If a `set` accessor of a child component property contains logic that causes rerendering of the parent component, an infinite rendering loop results.
+Don't place custom logic in the `get` or `set` accessor because component parameters are purely intended for use as a channel for a parent component to flow information to a child component. If a `set` accessor of a child component property contains logic that causes rerendering of the parent component, an infinite rendering loop results. Other side effects include unexpected extra renderings and parameter value overwrites.
 
 To transform a received parameter value:
 

aspnetcore/blazor/components/lifecycle.md

@@ -828,6 +828,80 @@ In the following example:
 
 :::moniker-end
 
+To display a loading indicator while the background work is taking place, use the following approach.
+
+Create a loading indicator component with a `Loading` parameter that can display child content in a <xref:Microsoft.AspNetCore.Components.RenderFragment>. For the `Loading` parameter:
+
+* When `true`, display a loading indicator.
+* When `false`, render the component's content (`ChildContent`). For more information, see [Child content render fragments](xref:blazor/components/index#child-content-render-fragments).
+
+`ContentLoading.razor`:
+
+```razor
+@if (Loading)
+{
+    <progress id="loadingIndicator" aria-label="Content loading…"></progress>
+}
+else
+{
+    @ChildContent
+}
+
+@code {
+    [Parameter]
+    public RenderFragment? ChildContent { get; set; }
+
+    [Parameter]
+    public bool Loading { get; set; }
+}
+```
+
+:::moniker range=">= aspnetcore-6.0"
+
+To load CSS styles for the indicator, add the styles to `<head>` content with the <xref:Microsoft.AspNetCore.Components.Web.HeadContent> component. For more information, see <xref:blazor/components/control-head-content>.
+
+```razor
+@if (Loading)
+{
+    <!-- OPTIONAL ...
+    <HeadContent>
+        <style>
+            ...
+        </style>
+    </HeadContent>
+    -->
+    <progress id="loadingIndicator" aria-label="Content loading…"></progress>
+}
+else
+{
+    @ChildContent
+}
+
+...
+```
+
+:::moniker-end
+
+Wrap the component's Razor markup with the `ContentLoading` component and pass a value in a C# field to the `Loading` parameter when initialization work is performed by the component:
+
+```razor
+<ContentLoading Loading="@loading">
+    ...
+</ContentLoading>
+
+@code {
+    private bool loading = true;
+    ...
+
+    protected override async Task OnInitializedAsync()
+    {
+        await LongRunningWork().ContinueWith(_ => loading = false);
+    }
+
+    ...
+}
+```
+
 ## Blazor Server reconnection events
 
 The component lifecycle events covered in this article operate separately from [server-side reconnection event handlers](xref:blazor/fundamentals/signalr#reflect-the-server-side-connection-state-in-the-ui). When the SignalR connection to the client is lost, only UI updates are interrupted. UI updates are resumed when the connection is re-established. For more information on circuit handler events and configuration, see <xref:blazor/fundamentals/signalr>.

aspnetcore/blazor/components/rendering.md

@@ -326,4 +326,4 @@ The state manager approach is similar to the earlier case with <xref:System.Time
 <!-- UPDATE 10.0 Will be removed for a new feature in this area. 
                  Tracked by: https://github.com/dotnet/aspnetcore/issues/49056 -->
 
-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>.
+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/routing.md

@@ -1056,6 +1056,7 @@ Navigation.GetUriWithQueryParameters("{URI}", {PARAMETERS})
 Supported types are identical to supported types for route constraints:
 
 * `bool`
+* `DateOnly`
 * `DateTime`
 * `decimal`
 * `double`
@@ -1064,6 +1065,7 @@ Supported types are identical to supported types for route constraints:
 * `int`
 * `long`
 * `string`
+* `TimeOnly`
 
 Supported types include: