-
Notifications
You must be signed in to change notification settings - Fork 963
fix: correct markup for Abbr component #19317
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
pronunciation: Pronunciation; | ||
}; | ||
|
||
function assertAccessibleLabel({ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Got rid of the test helper because it felt like we were binding all our tests to a shallow abstraction
children === children.toUpperCase() | ||
? "tracking-wide" | ||
: "tracking-normal", | ||
"no-underline tracking-normal", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wish we understood where the underline is coming from. these kinds of conflicts are so annoying. can we at least add a TODO to clean this up one day?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So, the funny thing is, abbr
elements have an underline by default in normal HTML – it's MUI that somehow overrode it
I actually don't think we should do anything – once MUI is out, we should be much closer to "normal" CSS, and this behavior would be 100% expected
Fixes some accidental styling issues introduced in #19242
Changes made
className
prop so that we can override the styles as neededNotes