Merge lp:~jcsackett/launchpad/better-status-colors into lp:launchpad

Proposed by j.c.sackett
Status: Merged
Approved by: j.c.sackett
Approved revision: no longer in the source branch.
Merged at revision: 15372
Proposed branch: lp:~jcsackett/launchpad/better-status-colors
Merge into: lp:launchpad
Diff against target: 30 lines (+3/-2)
2 files modified
lib/canonical/launchpad/icing/css/colours.css (+1/-1)
lib/lp/app/javascript/choiceedit/assets/choiceedit-core.css (+2/-1)
To merge this branch: bzr merge lp:~jcsackett/launchpad/better-status-colors
Reviewer Review Type Date Requested Status
Curtis Hovey (community) code Approve
Review via email: mp+109000@code.launchpad.net

Commit message

Updates colors and choice-link style to make division between choice title and chioce description clearer in cases like INVALID bug status.

Description of the change

Summary
=======
On the new bugstatus picker, the INVALID and WONTFIX statuses are not clearly
separated from the description text, as they have the same color.

This color--gray--is a pretty good choice for the statuses, but the issue of
separation is important. This branch attempts to resolve the problem with a
lighter gray and some font-weight changes.

Implementation
==============
The font-weight of choiceedit choice-links is changed to bold; as these
*titles*, the use of bold text is not inconsistent.

The color of the INVALID and WONTFIX statuses is changed to light gray; this
is still readable, while maintaining the semantics of gray text and being
separate from the default gray we use in text.

The changes as seen in the bug status choiceedit can be seen here: http://people.canonical.com/~jc/images/bugstatus-color-issue.png

Tests
=====
None.

QA
==
Verify the presentation is right on qastaging.

LoC
===
This is part of the disclosure work.

Lint
====
Our css files don't appear to conform to the rules in our css linter; almost
every line came up as an error, and so the linting is not included. The
changed lines are consistent with the formats in the file.

To post a comment you must log in.
Revision history for this message
Curtis Hovey (sinzui) wrote :

+1 for the bold

I think some of our shades of grey violate WCAG. We need more contrast. #666 is the lightest text can be. I bet we have shades that are higher.
/me looks

PSU has a cheatsheet for us! http://accessibility.psu.edu/contrasthtml

I see in colour.css that we use #999, #bebebe, and gray. We use these for status colours. I see in form.css that .formHelp used for descriptions is #777. I think the last must be changed to #666, and we may want the others to be #555

Can you try darker colours?

review: Needs Information (ui)
Revision history for this message
j.c.sackett (jcsackett) wrote :

Sure, I'll play with colors a bit. Sorry I missed you on IRC.

Revision history for this message
j.c.sackett (jcsackett) wrote :
Revision history for this message
Curtis Hovey (sinzui) wrote :

This is a very nice improvement. Thank you.

review: Approve (code)

Preview Diff

[H/L] Next/Prev Comment, [J/K] Next/Prev File, [N/P] Next/Prev Hunk
1=== modified file 'lib/canonical/launchpad/icing/css/colours.css'
2--- lib/canonical/launchpad/icing/css/colours.css 2012-03-07 20:57:20 +0000
3+++ lib/canonical/launchpad/icing/css/colours.css 2012-06-06 22:51:27 +0000
4@@ -107,7 +107,7 @@
5 }
6 .statusINVALID, .statusINVALID a,
7 .statusWONTFIX, .statusWONTFIX a {
8- color: gray;
9+ color: #555;
10 }
11 .importanceCRITICAL, .importanceCRITICAL a {
12 color: red;
13
14=== modified file 'lib/lp/app/javascript/choiceedit/assets/choiceedit-core.css'
15--- lib/lp/app/javascript/choiceedit/assets/choiceedit-core.css 2012-05-16 02:09:30 +0000
16+++ lib/lp/app/javascript/choiceedit/assets/choiceedit-core.css 2012-06-06 22:51:27 +0000
17@@ -47,11 +47,12 @@
18 }
19 .yui3-ichoicelist-content .choice-link {
20 padding: 0;
21+ font-weight: bold;
22 }
23 .yui3-ichoicelist-content .choice-description {
24 font-weight: normal;
25 padding: 0;
26- color: #777;
27+ color: #666;
28 }
29 .yui3-ichoicelist-content .choice-link:hover {
30 text-decoration: underline;