Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Reintroduce Hidden component

See original GitHub issue

Reintroduce the hidden component.

https://material-ui.com/components/hidden/

The removal of the hidden compatibility breaks backwards compatibility. Currently the sx property makes it difficult to replicate the functionally of the hidden component. I think it has been prematurely removed.

For example:

<Hidden smDown><Button display='flex' /><Hidden/>

becomes,

<Button sx={{ display: { xs: "none", sm: "none", md: "flex", lg: "flex", xl: "flex" }}} />

Having to list all the breakpoints in the example above isn’t ideal. Hidden supported this use case well.

Issue Analytics

State:
Created 2 years ago
Comments:5 (3 by maintainers)

Top GitHub Comments

5reactions

oliviertassinaricommented, May 31, 2021

I have stopped listening to issues for the last 3 weeks and will likely continue going forward. I was planning to open the same issue when I realized it was already created. It seems that the removal of the <Hidden> component was premature. We got a lot more people complaining about this one than most of the other BCs.

My main concern is that the migration path is only fully available since v5, people on v4 don’t have a smooth transition. I propose we introduce the component back but deprecated. cc @mui-org/core.

0reactions

GDownescommented, May 21, 2021

@mnajdova Thanks for the clarification. That makes sense, closing. I still think that Hidden should be deprecated more slowly.