Closed
Bug 189842
Opened 22 years ago
Closed 22 years ago
Highlighting in about:config is too dark.
Categories
(SeaMonkey :: Preferences, defect)
SeaMonkey
Preferences
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: jasonb, Assigned: bugs)
Details
Attachments
(2 files, 1 obsolete file)
7.01 KB,
image/png
|
Details | |
700 bytes,
patch
|
neil
:
review+
jag+mozilla
:
superreview+
asa
:
approval1.3b+
|
Details | Diff | Splinter Review |
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3b) Gecko/20030120 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3b) Gecko/20030120 The new about:config menus (from bug 107418) are great, but there's one small problem. When you have an item highlighted, the background colour is so dark that it's almost impossible to determine what the preference is. You pretty much have to click somewhere else to be able to read the entry again. The background colour should be made lighter. Reproducible: Always Steps to Reproduce: 1. Enter "about:config" into the URL bar. 2. Highlight an entry. Actual Results: The highlight colour is so dark that it's almost impossible to make out the text of the preference highlighted. Expected Results: The highlight colour should be lighter such that there is problem reading the selected preference.
Comment 1•22 years ago
|
||
The problem is that the text color for the prefs is hardcoded green/blue while the selection color depends on the OS color scheme. This may work with some color schemes, but fail with others. See http://lxr.mozilla.org/seamonkey/source/xpfe/global/resources/content/config.css#50 for the hardcoding of the pref color. Solution: choose other colors for the prefs texts that depend on the color scheme (about:plugins is nicely styled this way!). Best way is probably to use text style rather than text color for distinction between user set and default prefs. Maybe I'll attach a patch in a while (no promise made!). CCing neil@parkwaycc.co.uk who fixed bug 107418 and made the prefs selectable (I think). Sorry if you didn't like me to do that...
Comment 2•22 years ago
|
||
This patch makes all text in about:config use the system color for such text. User set preferences are bold now (whole line) to make a difference to prefs at default (no text style). Locked prefs are set to italic, but I have never seen such ones anyway... (Previously: green, blue, red) The first column is now not emphasized any more (was bold previously), but I don't see any need for that - it's a own column after all and easily distinguished from the others that way. And its content does not justify an emphasis IMO. I just tested this patch with various different Windows color schemes and setting/unsetting user prefs. It works all well, the colors are as one would expect and highlighted items look just like any other highlighted text in any application. Any objections against this way to go?
Comment 3•22 years ago
|
||
Looks like this now. (With my personal color scheme, but colors change as schemes are switched.)
Reporter | ||
Comment 4•22 years ago
|
||
> Any objections against this way to go?
It looks good to me!
Comment 5•22 years ago
|
||
Your patch doesn't match your screenshot - currently the preference name column is bold, but it isn't in your screenshot, yet you aren't turning it off...
Comment 6•22 years ago
|
||
Ooops, sorry. This new patch also removes the bold style from the first column as the first one already was supposed to do. (When transferring the canges in my build to the file I checked out using CVS I forgot that one change). Now it matches the screenshot.
Attachment #112109 -
Attachment is obsolete: true
Comment 7•22 years ago
|
||
Comment on attachment 112145 [details] [diff] [review] Real patch Well, I don't have any better ideas, perhaps when the skinVersion next changes we can make about:config themable.
Attachment #112145 -
Flags: review+
Comment 8•22 years ago
|
||
Neil: great! Should I try and get a sr= somewhere? or is yours a rs= ? Can you check it in or find somebody to do so afterwards? Or should I find somebody? I think I know somebody who would do it. It would be nice if this went in before the freeze because that new feature (editing prefs here) will be one of the new things in 1.3b - too bad (although still usable) if it still had this problem...
Comment 9•22 years ago
|
||
Comment on attachment 112145 [details] [diff] [review] Real patch Requesting sr= from jaggernaut@netscape.com. It would be nice to have this very small fix in 1.3b because Neil's changes on about:config are a bit better usable with it.
Attachment #112145 -
Flags: superreview?(jaggernaut)
Comment 10•22 years ago
|
||
Comment on attachment 112145 [details] [diff] [review] Real patch sr=jag
Attachment #112145 -
Flags: superreview?(jaggernaut) → superreview+
Comment 11•22 years ago
|
||
Comment on attachment 112145 [details] [diff] [review] Real patch Requesting approval for 1.3b: Risk: minor low risk css changes for 'about:config'. Benefit: they make Neil's new functionality of that page better usable.
Attachment #112145 -
Flags: approval1.3b?
Comment 12•22 years ago
|
||
Comment on attachment 112145 [details] [diff] [review] Real patch a=asa (on behalf of drivers) for checkin to 1.3beta.
Attachment #112145 -
Flags: approval1.3b? → approval1.3b+
Comment 13•22 years ago
|
||
Fix checked in.
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → FIXED
Comment 14•22 years ago
|
||
looks fine --tested with 2003.02.12 comm trunk bits (win2k, linux rh8.0, mac 10.2.3).
Status: RESOLVED → VERIFIED
OS: Windows XP → All
Hardware: PC → All
Updated•20 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•