UX: Batch actions should start out disabled
Bug #1570455 reported by
Diana Whitten
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Dashboard (Horizon) |
Expired
|
Wishlist
|
Unassigned | ||
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.
Revision history for this message
| Diana Whitten (hurgleburgler) wrote | #1 |
Revision history for this message
| Akihiro Motoki (amotoki) wrote | #2 |
| Changed in horizon: | |
| assignee: | Diana Whitten (hurgleburgler) → nobody |
| milestone: | next → none |
| status: | Triaged → Incomplete |
Revision history for this message
| Launchpad Janitor (janitor) wrote | #3 |
| Changed in horizon: | |
| status: | Incomplete → Expired |
To post a comment you must log in.
I am not sure what is the actual problem... Could you provide more detail context?