Closed Bug 37529 Opened 24 years ago Closed 24 years ago

Poor Legability of drop menus[modern skin]

Categories

(SeaMonkey :: General, defect, P3)

defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: lake, Assigned: german)

References

Details

The legability is poor on the drop menus for the Toolbar bookmarks menu and the 
task bar items. Usability studies and random comments confirm that the users are 
having difficulty reading the menu items. 
The character definition was poor due to blending of the edges from the low 
contrast in the back ground and forground colors in combination with the font 
size. 
This concerns the legability and recognition of the characters and words not the 
Icons in either the toolbar or the task bar.

Expected Results:  Skins describing fonts for drop menus chould ensure 
legability using high contrast and appropriate font size combinations. Given a 
larger font or different (high contrast) values on forground and back ground the 
legability would increase. 

Possibly related to bugs 29103-flat look, 29105-Chrome color choice, and 
29137-Ugly baby,
The size issue should be fixed once Seamonkey starts using CSS2 system UI fonts.

The color issue has been largely fixed, except for menus coming off the taskbar

which are still light blue on dark blue (rather than black on gray).

Blocks: 29105
Depends on: 16729, 30715
Reassigning to German
Assignee: bdonohoe → german
set to M18 for final decision. 
Target Milestone: --- → M18
the menus coming off the taskbar have also been fixed. marking as fixed
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
Summary: Poor Legability of drop menus → Poor Legability of drop menus[modern skin]
Chaning the qa contact on these bugs to me. MPT will be moving to the 
owner of this component shortly. I would like to thank him for all his hard 
work as he moves roles in mozilla.org...Yada, Yada, Yada...
QA Contact: mpt → zach
Component: User Interface Design → Browser-General
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.