Closed Bug 1376358 Opened 9 years ago Closed 8 years ago

Don't use "zillahighlight" for meaningful content

Categories

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

All
Other
enhancement
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: krinkle, Unassigned)

References

Details

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

Attachments

(1 file)

What did you do? ================ Reading content. What happened? ============== H3 text becomes very unusable in the beta because of it using the zillahighlight font. What should have happened? ========================== I would strongly recommend not to make the mistake of rendering body content in a font intended for logos and slogans, where long-form reading and cognitive overhead don't matter. This is not how you apply visual identity. Aside from being very distracting, it also adds just a little extra overhead and confusion to make the reading experience highly disruptive. It also constantly makes me irk due to thinking the text is selected. Both in the body content headings (where the text is unexpectedly white on black), as well as in the footer (where background is black with white text, except for again, the headings being negated and appearing selected and too distracting). Is there anything else we should know? ====================================== At the very least, if you absolutely must insist on negative text, do it in CSS so that the characters aren't overlapping each other with inconsistent edges. (See screenshot)
Attached image Screenshot
We're removing zilla highlight from the beta today and will investigate other ways to achieve a similar but more readable effect. Thanks!
Zillahighlight is gone and it's not coming back.
Status: UNCONFIRMED → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Product: developer.mozilla.org → developer.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: