yahoo-eng-team team mailing list archive

["Gary W. Smith" <gary.w.smith@xxxxxx>]

Broadened the description, since this UX is pervasive.

** Description changed:

- How to reproduce
+ 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")
- 
- There are some concerns that when the delete button is not available, it
- could confuse users why the button disappears.  One suggestion is that
- instead of hiding it , make deletable button disabled.
- 
- We need UX folks overall strategy to  help resolve this kind of UX
- concern.

** Changed in: horizon
       Status: New => Opinion

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1400566

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

Status in OpenStack Dashboard (Horizon):
  Opinion

Bug description:
  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")

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1400566/+subscriptions