Provide a simple opt-out option of preserving statically rendered components during navigation

[IevgeniiKunshchykov]

Is there an existing issue for this?

• [X] I have searched the existing issues

Describe the bug

The problem is : when I refresh static page that contains interactive component then interactive component is not refreshed.

I've got an app :

When I click remove last button and refresh page using such code : var absoluteUri = this.NavigationManager.ToAbsoluteUri(this.NavigationManager.Uri); this.NavigationManager.NavigateTo(absoluteUri.AbsolutePath);

Then page is refreshed but interactive component not

If I provide a @key to my interactive component inside static one

Then all works as expected and interactive component is recreated and displayed

Here is link to repo https://github.com/IevgeniiKunshchykov/InteractivePageUpdateInsideStatic.git

Can someone explain me that behavior? Why is that done in such way? Why interactive component is not reinitialized without @key?

Thank you!

Expected Behavior

Interactive component is reinitialized inside static one

Steps To Reproduce

No response

Exceptions (if any)

No response

.NET Version

No response

Anything else?

No response

[mkArtakMSFT]

Thanks for contacting us. The behavior you're observing is by-design. What is happening here is that Blazor has some special features that are available to statically rendered components. One of these features is the DOM Merging logic, which is used to maintain as much unchanged content from the previous page as possible. That logic utilizes the @key directive to match components. That's why, when you choose to use different keys the content is being replaced and you get the desired behavior.

I'll update the title of this issue and we'll use this going forward to see if we need to come up with some simpler / more intuitive way of opting-out from this behavior. Something like @do-not-preserve (bad name probably, but we'll come up with a better one later).

[garrettlondon1]

@mkArtakMSFT I understand it was initially by design but its very weird telling a parent static page to refresh, and an interactive island inside of that parent page does not reinitialize

If you forceload the navigation manager it will reopen a new circuit

I think the default navigation manager behavior should reinitialize all interactive components by default when a parent static page is reloaded

The @key has no use on a static page, neither does @do-not-preserve, we should opt in to @preserve