In v4, looking at the chips demo, the css rules specificity is dependent on the order of the css, which is problematic when using any build tools that might change the order
Expected Behavior 🤔
The should be no specificity conflict between classes.
Current Behavior 😯
Looking at the chips demo on your website, the generated code has both a .MuiChip-avatarColorPrimary and .MuiAvatar-colorDefault class defining the color and background-color css attributes. Same thing happens with .MuiChip-avatar and .MuiAvatar-root both defining width, height and font-size.
Steps to Reproduce 🕹
in https://material-ui.com/components/chips/, inpect element on the first blue chip shows:
In v4, looking at the chips demo, the css rules specificity is dependent on the order of the css, which is problematic when using any build tools that might change the order
Expected Behavior 🤔
The should be no specificity conflict between classes.
Current Behavior 😯
Looking at the chips demo on your website, the generated code has both a
.MuiChip-avatarColorPrimaryand.MuiAvatar-colorDefaultclass defining thecolorandbackground-colorcss attributes. Same thing happens with.MuiChip-avatarand.MuiAvatar-rootboth definingwidth,heightandfont-size.Steps to Reproduce 🕹
in https://material-ui.com/components/chips/, inpect element on the first blue chip shows:
