Closed Bug 84597 Opened 23 years ago Closed 23 years ago

radio button dots and toggle checkmarks are hard coded black

Categories

(SeaMonkey :: Preferences, defect)

x86
Windows 95
defect
Not set
normal

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 75971

People

(Reporter: duanev, Assigned: mcafee)

Details

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Win95; en-US; rv:0.9.1) Gecko/20010607
BuildID:    2001060703

I am constantly surprised by how many modern GUIs continue to
hard code color values or otherwise assume light color
backgrounds.  I use light colors on a dark background and even
here in 2001 I frequently find dialogs I can't read or interperet
becuase of these kinds of assumptions.  I've attached text that
can be pasted into notepad, saved as a .reg, and merged with a
registry (for 95, but maybe 98, 2000, etc. too).  Switch to the
scheme named "Duane's" and call up the Mozilla peferences dialog.
Look for black indicators which are now nearly impossible to see.



Reproducible: Always
Steps to Reproduce:
1. Install attached 95 color scheme into the registry
2. Select "Duane's" color scheme on the desktop properties
3. Call up the Mozilla prefernces dialog, change some toggle

Expected Results:  I am suggesting to GUI designers the idea of a high contrast
automatic background color algorithm based on HSV values.  With
RGB it is difficult to automatically find good compliment colors
that doesn't gross people out, but with HSV I suspect it is
relatively simple.  Convert the RGB to HSV, pick an "opposite"
hue or value (or both), and convert back to RGB.

Actually a background color check could be performed to ensure
sufficient contrast at a very low level.  If a foreground and
background pair checked by an algorithm like the above do not
find sufficient contrast, it can modify the background to ensure
readability.  Comments?



REGEDIT4

[HKEY_CURRENT_USER\Control Panel\Appearance\Schemes]
"Duane's"=hex:01,00,00,43,fe,c0,01,00,00,00,10,00,00,00,10,00,00,00,12,00,00,\
  00,12,00,00,00,f5,ff,ff,ff,00,00,00,00,00,00,00,00,00,00,00,00,bc,02,00,00,\
  00,00,00,00,00,00,00,00,4d,53,20,53,61,6e,73,20,53,65,72,69,66,00,20,2c,00,\
  00,a4,7e,00,00,8c,7e,63,00,00,00,00,00,01,00,0f,00,00,00,0f,00,00,00,f8,ff,\
  ff,ff,00,00,00,00,00,00,00,00,00,00,00,00,90,01,00,00,00,00,00,00,00,00,00,\
  00,4d,53,20,53,61,6e,73,20,53,65,72,69,66,00,20,2c,00,00,a4,7e,00,00,8c,7e,\
  63,00,00,00,00,00,01,00,12,00,00,00,12,00,00,00,f5,ff,ff,ff,00,00,00,00,00,\
  00,00,00,00,00,00,00,90,01,00,00,00,00,00,00,00,00,00,00,4d,53,20,53,61,6e,\
  73,20,53,65,72,69,66,00,20,2c,00,00,a4,7e,00,00,8c,7e,63,00,00,00,00,00,01,\
  00,f5,ff,ff,ff,00,00,00,00,00,00,00,00,00,00,00,00,90,01,00,00,00,00,00,00,\
  00,00,00,00,4d,53,20,53,61,6e,73,20,53,65,72,69,66,00,20,2c,00,00,a4,7e,00,\
  00,8c,7e,63,00,00,00,00,00,01,00,f5,ff,ff,ff,00,00,00,00,00,00,00,00,00,00,\
  00,00,90,01,00,00,00,00,00,00,00,00,00,00,4d,53,20,53,61,6e,73,20,53,65,72,\
  69,66,00,20,2c,00,00,a4,7e,00,00,8c,7e,63,00,00,00,00,00,01,00,f8,ff,00,00,\
  00,00,00,00,90,01,00,00,00,00,00,00,00,00,4d,53,20,53,61,6e,73,20,53,65,72,\
  69,66,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,bf,bf,bf,00,\
  40,00,00,00,00,00,ff,00,53,53,53,00,80,80,80,00,53,53,53,00,00,00,00,00,00,\
  00,00,00,ff,ff,ff,00,ff,ff,ff,00,80,80,80,00,80,80,80,00,53,53,53,00,00,00,\
  80,00,ff,ff,ff,00,80,80,80,00,53,53,53,00,53,53,53,00,00,00,00,00,c0,c0,c0,\
  00,bf,bf,bf,00,00,00,00,00,80,80,80,00,00,00,00,00,ff,ff,e1,00
Unfortunately, we use images for the checkmarks and dots in question... so there
is no way to easily adjust their color.  Duplicate of "dialog checkmarks are
always black (invisible with background)"

Once we have SVG we may be able to fix this problem.

*** This bug has been marked as a duplicate of 75971 ***
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
mass verification of duplicate bugs: to find all bugspam pertaining to this, set
your search string to "DuplicateBugsBelongInZahadum".

if you think this particular bug is *not* a duplicate, please provide a
compelling reason, as well as check a recent *trunk* build (on the appropriate
platform[s]), before reopening.
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.