-
-
Notifications
You must be signed in to change notification settings - Fork 37
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
MUI V5 precedence - nested classes? #38
Comments
Maybe related to mui/material-ui#28664 and not even in the scope of |
Damn it, it's not the expected behaviour indeed. Probably something that need to be addressed on the mui side though. Thank you for reporting |
I have opened an issue about it. In the meantime, since it looks like to be specifically related to the const ChipStyled= withStyles(Chip, {
"deleteIcon": {
"&&":{
"color": "red"
}
}
}); |
They closed it. So do I. I don't think it's up to me. Reopen if you think otherwise. |
Sounds good, ty for the fast help :) |
Hi there,
I'm currently trying out
tss-react
and noticed a roadblock, which I'm not sure how to solve it: I'm unable to change the color of thedeleteIcon
of aChip
since the original styles take precedence. I also followed the steps of the README, see here for a repro: https://stackblitz.com/edit/tss-react-aupnsq?file=Hello.tsxAs you can see, overriding the color in the theme works, but individually styling it with
withStyles
creates the wrong class order.Am I missing something obvious? Do I maybe somehow have to specify
MuiButtonBase-root-MuiChip-root
so it it's on the same level?The text was updated successfully, but these errors were encountered: