[Blazor] Prevent unwanted DOM merging during enhanced page updates

[MackinnonBuck]

There might be times when an enhanced page update results in DOM elements getting merged/recycled in an undesirable manner. This is fine in many cases but can sometimes cause strange side effects (e.g., weird CSS animations playing on merged elements).

We should consider introducing a data-key attribute that can be used to manually indicate that a DOM element can only be merged with another element with a matching data-key attribute.

A current workaround is to wrap content in an element with a unique tag name to prevent it from getting merged. This could be an unresolved custom element tag name, e.g., <pricing-grid>.

Thanks for contacting us.

We're moving this issue to the .NET 9 Planning milestone for future evaluation / consideration. We would like to keep this around to collect more feedback, which can help us with prioritizing this work. We will re-evaluate this issue, during our next planning meeting(s).
If we later determine, that the issue has no community involvement, or it's very rare and low-impact issue, we will close it - so that the team can focus on more important and high impact issues.
To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.

Thanks for contacting us.

We're moving this issue to the .NET 9 Planning milestone for future evaluation / consideration. We would like to keep this around to collect more feedback, which can help us with prioritizing this work. We will re-evaluate this issue, during our next planning meeting(s).
If we later determine, that the issue has no community involvement, or it's very rare and low-impact issue, we will close it - so that the team can focus on more important and high impact issues.
To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.