On map_app's I have seen a bad-looking behavior when the content shrinks and stretches depending on the size of its content, this causes the content of the component to be totally unattached from the initial display point (the menu button), I think (I haven't proved it yet) that it can be solved by using a min/max-width on the displayed component but if their different contents are totally different, it could cause a bad- looking display again...
I was thinking that we can make it optional to open the content of the buttons as a dialog, in that way, some of them (especially the ones that require more space) can be displayed on a bigger screen and the others in the same way...
On
map_app's I have seen a bad-looking behavior when the content shrinks and stretches depending on the size of its content, this causes the content of the component to be totally unattached from the initial display point (the menu button), I think (I haven't proved it yet) that it can be solved by using amin/max-widthon the displayed component but if their different contents are totally different, it could cause a bad- looking display again...I was thinking that we can make it optional to open the content of the buttons as a dialog, in that way, some of them (especially the ones that require more space) can be displayed on a bigger screen and the others in the same way...
Bad display:
screen-capture (2).webm
@12rambau what do you think?