yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #49529
[Bug 1557729] Re: Branding: Material: Angular vs. Django Table Action Danger Button Inconsistency
Reviewed: https://review.openstack.org/293117
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=88968353537c455d084fd1cca0a7405082d4b164
Submitter: Jenkins
Branch: master
commit 88968353537c455d084fd1cca0a7405082d4b164
Author: Diana Whitten <hurgleburgler@xxxxxxxxx>
Date: Tue Mar 15 11:08:57 2016 -0700
Angular vs. Django Table Danger Button Inconsistency
A button should have either btn-default OR btn-danger ... not both.
This also removes the flashing red change this problem caused when
adding a 'disabled' class to the button after its already been
rendered on the page.
Closes-bug: #1557729
Closes-bug: #1549957
Change-Id: I6e035868be4df653438b4d31b462729c3fe06d9f
** Changed in: horizon
Status: In Progress => Fix Released
--
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/1557729
Title:
Branding: Material: Angular vs. Django Table Action Danger Button
Inconsistency
Status in OpenStack Dashboard (Horizon):
Fix Released
Bug description:
https://i.imgur.com/KUHpaae.png
vs.
https://i.imgur.com/zicXft0.png
The morale of the story is ... a button should have either btn-default
OR btn-danger ... not both.
To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1557729/+subscriptions
References