Skip to content

Sections Pre6 updates #29795

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
guardrex merged 3 commits into from
Jul 13, 2023
Merged

Sections Pre6 updates #29795

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
c01a1b9
Sections Pre6 updates
guardrex Jul 13, 2023
abb38e6
Updates
guardrex Jul 13, 2023
3477d23
Updates
guardrex Jul 13, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 11 additions & 0 deletions aspnetcore/blazor/components/sections.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -78,3 +78,14 @@ When the `Counter` component is accessed, the `MainLayout` component renders the

> [!NOTE]
> `SectionOutlet` and `SectionContent` components can only set either `SectionId` or `SectionName`, not both.

## Section interaction with other Blazor features

A section interacts with other Blazor features in the following ways:

* [Cascading values](xref:blazor/components/cascading-values-and-parameters) flow into section content from where the content is defined by the `SectionContent` component.
* Unhandled exceptions are handled by [error boundaries](xref:blazor/fundamentals/handle-errors#error-boundaries) defined around a `SectionContent` component.
* A Razor component configured for streaming rendering also configures section content provided a `SectionContent` component to use streaming rendering.

<!-- UPDATE FOR 8.0 Add "streaming rendering" cross-link -->