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
As I saw that there was work done on the StatusCard I decided to open a Issue regarding some stuff that's been on my mind for quite some time.
So, currently Actions that are not available to the user, set the IconButton as disabled - for example for editing the device and deleting it. Why not just hide the button completely? It just takes up space when it's not needed (and there is no user action that can make it available to them).
Maybe - if there is consensus on this - I would be even prepared to invest some time and create a 'fluid' system, where first 4 available actions are displayed, and the rest are 'hidden' behind the 3 dots, like currently share/links/etc are.
The text was updated successfully, but these errors were encountered:
My main issue is that people would expect certain buttons in certain places. Moving buttons makes it harder to debug issues because buttons might be in different places. What is the problem with disabled buttons?
I just find it annoying and waste of space. I understand your position, but on the other hand relying on position of the buttons and not the buttons themselves is not that great. And now we have longer path than needed for some buttons, and completely wasted space for others. Which I find not optimal - and I think the icons (and the new tooltip) should be plenty enough to discern what is the action of the button?
As I saw that there was work done on the StatusCard I decided to open a Issue regarding some stuff that's been on my mind for quite some time.
So, currently Actions that are not available to the user, set the
IconButton
as disabled - for example for editing the device and deleting it. Why not just hide the button completely? It just takes up space when it's not needed (and there is no user action that can make it available to them).Maybe - if there is consensus on this - I would be even prepared to invest some time and create a 'fluid' system, where first 4 available actions are displayed, and the rest are 'hidden' behind the 3 dots, like currently share/links/etc are.
The text was updated successfully, but these errors were encountered: