Public bug reported:
Instead of starting out enabled and then becoming disabled, the most
common use case for batch actions is disabled. We should start out that
way first and then enable once we've crawled the table.
** Affects: horizon
Importance: Wishlist
Assignee: Diana Whitten (hurgleburgler)
Status: Triaged
** Tags: ux
** Attachment added: "button_disabled.gif"
https://bugs.launchpad.net/bugs/1570455/+attachment/4636896/+files/button_disabled.gif
--
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/1570455
Title:
UX: Batch actions should start out disabled
Status in OpenStack Dashboard (Horizon):
Triaged
Bug description:
Instead of starting out enabled and then becoming disabled, the most
common use case for batch actions is disabled. We should start out
that way first and then enable once we've crawled the table.
To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1570455/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
