UX Improvements: Buttons on Submitted Forms Do Not Deactivate
Bug #904030 reported by
Neil Johnston
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Dashboard (Horizon) |
Fix Released
|
Undecided
|
Neil Johnston | ||
Bug Description
input:submit buttons though-out the UI are only allowed to submit once. The preferred behaviour is once the button is clicked and the from submitted, the button is then deactivated and the primary class removed. This behaviour would signal to the user that the form submission is in process.
| Changed in horizon: | |
| assignee: | nobody → Neil Johnston (njohnston) |
Revision history for this message
| Openstack Gerrit (openstack-gerrit) wrote Fix merged to horizon (master) | #1 |
| Changed in horizon: | |
| status: | New → Fix Committed |
| Changed in horizon: | |
| milestone: | none → essex-2 |
| status: | Fix Committed → Fix Released |
| Changed in horizon: | |
| milestone: | essex-2 → 2012.1 |
To post a comment you must log in.
Reviewed: https:/
Committed: http://
Submitter: Jenkins
Branch: master
status fixcommitted
done
commit 96f5225f6d7863e
Author: Neil Johnston <email address hidden>
Date: Tue Dec 13 16:17:20 2011 -0800
blueprint Improve Dashboard UX
bug 904030
After the user submits a form by hitting a submit button (an application wide behaviour), the button now provides visual confrimation of it's submission by disabing though the removal of the primary class.
Change-Id: If52fe30b55b78a