Closed
Bug 402356
Opened 17 years ago
Closed 17 years ago
netError (and others) use hard-coded colors for warnings
Categories
(Core Graveyard :: Security: UI, defect, P2)
Core Graveyard
Security: UI
Tracking
(Not tracked)
RESOLVED
FIXED
mozilla1.9beta5
People
(Reporter: johnath, Assigned: takenspc)
References
Details
(Keywords: access)
Attachments
(4 files, 6 obsolete files)
|
48.18 KB,
image/png
|
Details | |
|
1.79 KB,
patch
|
Gavin
:
review+
|
Details | Diff | Splinter Review |
|
56.83 KB,
image/png
|
Details | |
|
27.06 KB,
image/png
|
beltzner
:
ui-review+
|
Details |
As part of his review of bug 401575, bz pointed out that netError.css (in both pinstripe and winstripe themes) uses hardcoded colours in cases where it should probably be using system colours. Specifically, the "securityOverrideContent" styles use a light yellow as a warning colour, hardcoded to #FFF090". In attempting to find a system colour to use instead, I found that both the notification bar styling for warnings and the error console styling for warnings in the log use hardcoded values, each different though all approximately "pale yellow."
This seems like it could have accessibility repercussions, though in the netError case specifically, the background colour does not communicate any additional information directly (i.e. it is not necessary to notice the colour in order to properly use the page.)
Updated•17 years ago
|
Flags: blocking1.9?
Comment 1•17 years ago
|
||
It's not about whether the background color communicates information. It's about the fact that the relevant style are:
112 #securityOverrideContent {
113 background-color: #FFF090; /* Pale yellow */
and
14 body {
17 color: -moz-FieldText;
(this is in the winstripe version of netError.css). Now there's no guarantee that that foreground color is different from #FFF090, since it's just a system color that depends on the OS theme. So it's possible for all the text inside #securityOverrideContent to be invisible.
Setting just one of background and foreground without setting the other is just generally a bad idea...
Updated•17 years ago
|
Priority: -- → P4
| Assignee | ||
Comment 3•17 years ago
|
||
A screenshot on the Linux/GTK2 (Nodoka-Midnight theme) which shows the problem.
I can hardly read it.
| Assignee | ||
Comment 4•17 years ago
|
||
A workaround patch which sets the foreground color of |#securityOverrideContent| to black.
| Assignee | ||
Comment 5•17 years ago
|
||
Comment 6•17 years ago
|
||
color: "black"; ?
| Assignee | ||
Comment 7•17 years ago
|
||
Oops!
A workaround patch fixes that typo.
Attachment #299379 -
Attachment is obsolete: true
| Assignee | ||
Comment 8•17 years ago
|
||
Patch for netError.css (winstripe/gnomestripe).
# notificationbar uses the combination of InfoBackground/Infotext too.
Attachment #299380 -
Attachment is obsolete: true
Attachment #299741 -
Attachment is obsolete: true
Attachment #303998 -
Flags: review?(gavin.sharp)
| Assignee | ||
Comment 9•17 years ago
|
||
Comment 10•17 years ago
|
||
Maybe it's just my monitor, or viewing angle, but I can hardly tell the difference between InfoBackground and white, unless I look very closely.
Comment 11•17 years ago
|
||
Cropped out too much of the background color in the previous screenshot, makes it look strange.
Attachment #305060 -
Attachment is obsolete: true
Updated•17 years ago
|
Attachment #305062 -
Flags: ui-review?(beltzner)
Comment 12•17 years ago
|
||
Comment on attachment 303998 [details] [diff] [review]
Patch for netError.css (winstripe/gnomestripe)
r=me on this, assuming beltzner is OK with the less differentiable color.
Attachment #303998 -
Flags: review?(gavin.sharp) → review+
Comment 13•17 years ago
|
||
Another option would be to keep #FFF090 as the background, and hard-code a black foreground. Means it might look weird with strange native themes, but will guarantee that it will always be legible (for people that can read black-on-yellowish, granted - pretty sure that's a large majority of our users :).
| Assignee | ||
Comment 14•17 years ago
|
||
> I can hardly tell the difference between InfoBackground and white, unless I look very closely.
I added another border. It helps emphasizing |InfoBackground|
| Assignee | ||
Comment 15•17 years ago
|
||
Updated•17 years ago
|
Assignee: kengert → taken.spc
Updated•17 years ago
|
Flags: tracking1.9+ → blocking1.9+
Priority: P4 → P2
Comment 16•17 years ago
|
||
Comment on attachment 305062 [details]
screenshot with patch (normal theme)
uir=beltzner
Attachment #305062 -
Flags: ui-review?(beltzner) → ui-review+
Updated•17 years ago
|
Attachment #303998 -
Flags: approval1.9?
Comment 17•17 years ago
|
||
Comment on attachment 303998 [details] [diff] [review]
Patch for netError.css (winstripe/gnomestripe)
This is a blocker, so no approval1.9 is required.
Attachment #303998 -
Flags: approval1.9?
Comment 18•17 years ago
|
||
Comment on attachment 305158 [details]
Screenshot with patch #2
beltzner: which screenshot of the two do you like the best?
Attachment #305158 -
Flags: ui-review?(beltzner)
Comment 19•17 years ago
|
||
I'm going to sit on this one before landing it, just until beltzner has looked at the second screenshot and picked which one he likes better.
Status: NEW → ASSIGNED
Keywords: checkin-needed
Comment 20•17 years ago
|
||
ThreeDShadow for the inner box looks cluttered. There should be no border or maybe ThreeDLightShadow, imho.
Updated•17 years ago
|
Keywords: checkin-needed
Updated•17 years ago
|
Attachment #305158 -
Attachment is obsolete: true
Attachment #305158 -
Flags: ui-review?(beltzner)
Updated•17 years ago
|
Attachment #305157 -
Attachment is obsolete: true
Comment 22•17 years ago
|
||
mozilla/toolkit/themes/winstripe/global/netError.css 1.9
mozilla/toolkit/themes/gnomestripe/global/netError.css 1.4
Status: ASSIGNED → RESOLVED
Closed: 17 years ago
Keywords: checkin-needed
Resolution: --- → FIXED
Target Milestone: --- → mozilla1.9beta5
Updated•9 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•