Table actions that are not allowed should be disabled instead of removed

[Gloria Gu]

Throughout horizon actions are controlled through their allowed function; if true, the button is shown; otherwise the button is hidden.

There are some concerns that when an action is not available, it could confuse users when the button disappears. One suggestion is that instead of hiding the button, make it disabled.

Before making this sweeping change, we should get direction from the UX folks.

How to reproduce:

Project - > volumes create a volume and attach an instance on it. The delete button should not show up for that volume.

Currently when volumes are in not deletable state, we use "allowed" method in the tables.py to hide the delete button. Volumes in the following states are deletable : DELETABLE_STATES = ("available", "error", "error_extending")

Note:

There are also another concern related to this that need UX advise, while the delete button in the row is not "allowed" for an undeletable item, the delete button is still there at the table level, the undeletable item still can be checked and performed the delete action on it. Not sure if I need different bug for this.

[Gloria Gu (gloria-gu)]

Hi Nijunj,

This is more of UX issue...better seek UX inputs for the changes. Thanks.

[Gary W. Smith (gary-w-smith)]

Broadened the description, since this UX is pervasive.