[release/8.0] Fix navigation for anchor inside <svg> element #53541
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
[release/8.0] Fix navigation for anchor inside
<svg>
elementBackport of #51706
Fixes multiple issues involving navigations initiated by clicks on
<a>
elements used in conjunction with<svg>
elements.Description
Makes the following improvements to how navigation interacts with
<svg>
elements:<a>
elements inside<svg>
elements to initiate enhanced navigations: Enhanced Navigation doesn't work inside SVG element #51705<svg>
elements to be marked withdata-enhance-nav="false"
to disable enhanced navigation: data-enhance-nav=false is ignored on <svg> elements #51440<a>
elements containing<svg>
elements to disable enhanced navigation viadata-enhanced-nav="false"
: Blazor web app (dotnet 8): data-enhance-nav="false" is not working when tag <a/> is wrapping some <svg/> #52205Fixes #51705
Fixes #51440
Fixes #52205
Customer Impact
Variations of this issue have been reported by several customers. Two of the abovementioned issues were reported before 8.0 GA, but this fix didn't make the GA cutoff. Since GA, a third variation of this issue has been reported, and it has received a couple upvotes by the community. There's no known workaround for these issues.
Regression?
This behavior has existed since the introduction of enhanced navigation (.NET 8).
Risk
The change is straightforward and pertains to a well-tested area of the framework.
Verification
Packaging changes reviewed?