Closed
Bug 412719
Opened 18 years ago
Closed 18 years ago
use -moz-cellhighlight* system color for selected items in non focused lists
Categories
(Toolkit :: UI Widgets, defect)
Tracking
()
RESOLVED
FIXED
mozilla1.9beta3
People
(Reporter: twanno, Assigned: twanno)
Details
Attachments
(1 file, 1 obsolete file)
|
8.71 KB,
patch
|
beltzner
:
approval1.9+
|
Details | Diff | Splinter Review |
Since -moz-cellhighlight is the correct color for selected cells in non focused trees / lists on Linux, (and -moz-cellhighlighttext the correct text color), this should be used for those elements and resembling elements in Mozilla too.
For Win32 nothing changes: -moz-cellhighlight* is the same color as -moz-Dialog*, but this makes it more distinguishable, and it will be easier to implement a new color for this if it is ever needed. What's more is that richlistbox.css from winstripe is still shared with gnomestripe.
For Mac I don't know what to do: currently for trees and lists -moz-mac-secundairyhighlight is used, but not for richlistboxes. Note that currently -moz-cellhighlight* is the same as -moz-Dialog*, but with the patch for bug 412281 in its current state -moz-cellhighlight will be the same as -moz-mac-secundairyhighlight.
Attachment #297479 -
Flags: review?(enndeakin)
Comment 1•18 years ago
|
||
Comment on attachment 297479 [details] [diff] [review]
patch
Looks OK, except for the one in gnomestripe/global/listbox.css :
+ color: -moz-cellhighlight;
should be -moz-cellhighlighttext
Attachment #297479 -
Flags: review?(enndeakin) → review+
| Assignee | ||
Comment 2•18 years ago
|
||
Fixed nit.
Attachment #297479 -
Attachment is obsolete: true
Attachment #298158 -
Flags: approval1.9?
Updated•18 years ago
|
Status: NEW → ASSIGNED
| Assignee | ||
Comment 3•18 years ago
|
||
Comment on attachment 298158 [details] [diff] [review]
patch (v1.1)
removing request for approval until things at bug 413272 are sorted out.
Attachment #298158 -
Flags: approval1.9?
| Assignee | ||
Comment 4•18 years ago
|
||
Comment on attachment 298158 [details] [diff] [review]
patch (v1.1)
Bug 413272 does not affect this patch: Requesting approval for a patch which makes selected items in unfocused trees / lists look better on Linux, by using an existing CSS system color, created for this purpose.
Attachment #298158 -
Flags: approval1.9?
Comment 5•18 years ago
|
||
Comment on attachment 298158 [details] [diff] [review]
patch (v1.1)
a=beltzner for 1.9, yay, look'n'feel
Attachment #298158 -
Flags: approval1.9? → approval1.9+
Updated•18 years ago
|
Keywords: checkin-needed
Comment 6•18 years ago
|
||
Checking in toolkit/themes/gnomestripe/global/listbox.css;
/cvsroot/mozilla/toolkit/themes/gnomestripe/global/listbox.css,v <-- listbox.css
new revision: 1.5; previous revision: 1.4
done
Checking in toolkit/themes/gnomestripe/global/tree.css;
/cvsroot/mozilla/toolkit/themes/gnomestripe/global/tree.css,v <-- tree.css
new revision: 1.10; previous revision: 1.9
done
Checking in toolkit/themes/gnomestripe/mozapps/extensions/extensions.css;
/cvsroot/mozilla/toolkit/themes/gnomestripe/mozapps/extensions/extensions.css,v <-- extensions.css
new revision: 1.2; previous revision: 1.1
done
Checking in toolkit/themes/winstripe/global/listbox.css;
/cvsroot/mozilla/toolkit/themes/winstripe/global/listbox.css,v <-- listbox.css
new revision: 1.10; previous revision: 1.9
done
Checking in toolkit/themes/winstripe/global/richlistbox.css;
/cvsroot/mozilla/toolkit/themes/winstripe/global/richlistbox.css,v <-- richlistbox.css
new revision: 1.3; previous revision: 1.2
done
Checking in toolkit/themes/winstripe/global/tree.css;
/cvsroot/mozilla/toolkit/themes/winstripe/global/tree.css,v <-- tree.css
new revision: 1.13; previous revision: 1.12
done
Checking in toolkit/themes/winstripe/mozapps/extensions/extensions.css;
/cvsroot/mozilla/toolkit/themes/winstripe/mozapps/extensions/extensions.css,v <-- extensions.css
new revision: 1.37; previous revision: 1.36
done
Status: ASSIGNED → RESOLVED
Closed: 18 years ago
Keywords: checkin-needed
Resolution: --- → FIXED
Target Milestone: --- → mozilla1.9 M11
You need to log in
before you can comment on or make changes to this bug.
Description
•