Closed Bug 948437 Opened 11 years ago Closed 11 years ago

On certain monitors the light, grayscale MDN site can be quite hard to read; it would be best to have a darker theme available or use a thicker typeface.

Categories

(developer.mozilla.org Graveyard :: Design, defect)

All
Other
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 924767

People

(Reporter: andrew.e.mauney, Unassigned)

Details

(Whiteboard: [specification][type:change])

What feature should be changed? Please provide the URL of the feature if possible. ================================================================================== The new MDN pages are harder to read on certain monitors due to the color palette and thinner typeface choices. This could be remedied through having a darker theme available What problems would this solve? =============================== Issues being viewed on monitors with varying contrast. It would also reduce eyestrain if a dev is working at night or in a poorly light area. Who would use this? =================== Especially people coding at night or who have a sensitivity to brighter colors/light. What would users see? ===================== Some kind of light/dark toggle in the top utility bar or as a setting in their user/persona preferences. What would users do? What would happen as a result? =================================================== For logged in users, it would stay this way until otherwise changed. For non-logged in users it would more than likely need to be a cookie that would persist for roughly a month. Is there anything else we should know? ====================================== I have noticed this problem on my DELL and Samsung monitors along with a coworker's Apple 30' Cinema display. When I viewed the site it was quite a shock to my eyes.
Component: General → Design / user experience
Status: UNCONFIRMED → RESOLVED
Closed: 11 years ago
Resolution: --- → DUPLICATE
Product: developer.mozilla.org → developer.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.