Bug 812849 - The "OK" and "Cancel" colors are not consistent
Summary: The "OK" and "Cancel" colors are not consistent
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: ovirt-node
Version: 6.3
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Joey Boggs
QA Contact: Virtualization Bugs
URL:
Whiteboard:
: 815285 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-04-16 12:37 UTC by shine
Modified: 2016-04-26 13:57 UTC (History)
12 users (show)

Fixed In Version: ovirt-node-2.3.0-4.el6
Doc Type: Bug Fix
Doc Text:
Previously, the colors of the OK and Cancel buttons were not consistent across all screens. Now, all screens use consistent colors for the OK and Cancel buttons.
Clone Of:
Environment:
Last Closed: 2012-07-19 14:20:52 UTC
Target Upstream Version:


Attachments (Terms of Use)
GrayButtonAfterInvalidNFSEntry (176.28 KB, application/x-gzip)
2012-04-16 12:37 UTC, shine
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2012:0741 0 normal SHIPPED_LIVE ovirt-node bug fix and enhancement update 2012-07-19 18:10:46 UTC

Description shine 2012-04-16 12:37:18 UTC
Created attachment 577701 [details]
GrayButtonAfterInvalidNFSEntry

Description of problem:
 The "OK" and "Cancel" colour are not consistent.


 Version-Release number of selected component (if applicable):
 rhev-hypervisor6-6.3-20120411.1

 How reproducible:
 100%

 Steps to Reproduce:
 1. Install rhevh on local host;
 2. Scroll to network, configure the nic and press "Apply" [GrayOKButtonOnNicConfiguration.png]
 3. Scroll to Security menu, choose or cancel the ssh;
 4. Scroll to CIM menu, enable or disable the CIM;
 5. Scroll to Kernel Dump menu, Configure NFS/SSH with invalid information;
 6. Scroll to RHN menu, configure RHN with invalid URL or CA;
 7. Press "F2" on keyboard;

 Actual results:
 1. Gray "OK" after configure nic and apply.
 2. Gray "OK" after change the status of the SSH.
 3. Red "OK" after configure the CIM configuration and apply.
 4. Gray "OK" in Kernel Dump configuration[GrayButtonAfterInvalidNFSEntry.png].
 5. The colour of the "OK" in RHN Satellite configuration with invalid URL or CA is red.
 6. Gray "OK" after press “F2”[GrayOKButtonAfterF2.png].

 Expected results:
 It would be better if the colour of the "OK" or "Cancel" is consistent.

 Additional info:

Comment 3 Mike Burns 2012-04-23 15:27:38 UTC
*** Bug 815285 has been marked as a duplicate of this bug. ***

Comment 5 Guohua Ouyang 2012-04-28 03:09:07 UTC
verified with rhevh-6.3-20120426.2 build, all buttons is gray and the text is red.

Comment 6 Mike Burns 2012-06-13 17:31:39 UTC
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
Previously, the colors of the OK and Cancel buttons were not consistent across all screens.  Now, all screens use consistent colors.

Comment 7 Stephen Gordon 2012-06-13 19:13:55 UTC
    Technical note updated. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    Diffed Contents:
@@ -1 +1 @@
-Previously, the colors of the OK and Cancel buttons were not consistent across all screens.  Now, all screens use consistent colors.+Previously, the colors of the OK and Cancel buttons were not consistent across all screens.  Now, all screens use consistent colors for the OK and Cancel buttons.

Comment 9 errata-xmlrpc 2012-07-19 14:20:52 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2012-0741.html


Note You need to log in before you can comment on or make changes to this bug.