Skip to content

Don't break interactive components when their parent static content is updated #48764

Closed
@SteveSandersonMS

Description

@SteveSandersonMS

When streaming SSR, progressively-enhanced navigation, or progressively-enhanced form posts update part of the DOM dynamically, we have to make sure they behave sensibly when part of that DOM structure is an interactive component.

  • Min bar: destroy the old interactive component and activate a new one
  • Better: preserve the old interactive component, but ignore any new params supplied by the updated static content
  • Best: ... also pass in new params from the updated static content

We likely only have capacity for a relatively basic implementation here, so may be limited to the min bar.

Metadata

Metadata

Assignees

Labels

area-blazorIncludes: Blazor, Razor ComponentsenhancementThis issue represents an ask for new feature or an enhancement to an existing onefeature-full-stack-web-uiFull stack web UI with Blazor

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions