[TreeView] TreeItem label is two levels of specificity instead of one

[david-ic3]

Some styles applied to TreeItem label are not applied (the class order is wrong).

You can check the example : https://codesandbox.io/s/gmailtreeview-material-demo-forked-s6z3q

font size should be 45px.

Tested on alpha.29, thank you very much for doing Material-UI ❤️

Search keywords:

[support]

👋 Thanks for using Material-UI!

We use GitHub issues exclusively as a bug and feature requests tracker, however,
this issue appears to be a support request.

For support, please check out https://material-ui.com/getting-started/support/. Thanks!

If you have a question on StackOverflow, you are welcome to link to it here, it might help others.
If your issue is subsequently confirmed as a bug, and the report follows the issue template, it can be reopened.

[oliviertassinari]

tip: check the CSS specificity of your selector (.css-ehlda4-MuiTreeItem-content .MuiTreeItem-label)

[oliviertassinari]

Actually, @mnajdova would it be worth flattening?

https://github.com/mui-org/material-ui/blob/58c7e708a419bc8895774e964b8ef00b55d045ac/packages/material-ui-lab/src/TreeItem/TreeItem.js#L119

I wonder, not sure.

[david-ic3]

Sorry, missing something, but this is the code generated by the TreeItem component (.css-ehlda4-MuiTreeItem-content .MuiTreeItem-label). I'd expect the css rule label to work as it is doing in v4.

The example we put here is using the Google TreeItem example Material-UI (actually check the difference between the same example between v5 and v4).

br,

[mnajdova]

Actually, @mnajdova would it be worth flattening?

https://github.com/mui-org/material-ui/blob/58c7e708a419bc8895774e964b8ef00b55d045ac/packages/material-ui-lab/src/TreeItem/TreeItem.js#L119

I wonder, not sure.

Agree, we should re-implement the TreeItemContent component to follow the implementation of the other components. Then we won't need to increase the specificity.

[github-actions]

⚠️ This issue has been closed.
If you have a similar problem, please open a new issue and provide details about your specific problem.
If you can provide additional information related to this topic that could help future readers, please feel free to leave a comment.

How did we do @david-ic3?
Your experience with our support team matters to us. If you have a moment, please share your thoughts through our brief survey.