fix(mui): remove nested interactive elements from button components #7094
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.
Summary
Changes
componentproptextDecoration: "none"style to the Button's sx proponClickhandler to the Button componentContext
The previous implementation wrapped a
<Button>element inside a<LinkComponent>(anchor tag), creating nested interactive elements. This violates accessibility guidelines and causes issues:Solution
Material UI's Button component supports rendering as different components via the
componentprop. By passingcomponent={LinkComponent}, the Button renders directly as a link, maintaining all navigation functionality without the nested structure.Test Plan
Affected Components
Resolves #7085