You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 5, 2024. It is now read-only.
Hello, I was trying to make a sidenav with an item stuck to the bottom of it using flex/layout. But it wasn't working until I switched the display:block to display:flex and added layout="column" to the md-sidenav. Is there any reason why block is the default? I also found it was the default on md-content which also caused problems with using flex. Let me know if you need a better example.
The text was updated successfully, but these errors were encountered:
epelc
changed the title
Why does md-sidenav have display:block
Why does md-sidenav use display:block instead of display:flex
Nov 22, 2014
It may be a bug with an accessibility feature of the sidenav--at some point they were changed to really hide when they aren't visible by using display: none and display: block. display: flex probably should have been used for the open state instead. cc @ajoslin
@marcysutton Thanks for the info. I want to experiment more with it because iirc md-content also needed display:flex to expand correctly in the sidenav. Maybe this effects more elements I dont know yet though.
Hello, I was trying to make a sidenav with an item stuck to the bottom of it using flex/layout. But it wasn't working until I switched the
display:block
todisplay:flex
and addedlayout="column"
to the md-sidenav. Is there any reason why block is the default? I also found it was the default on md-content which also caused problems with using flex. Let me know if you need a better example.The text was updated successfully, but these errors were encountered: