Last modified: 2014-10-04 06:48:44 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T73240, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 71240 - Re-evaluate serif font stack for headers
Re-evaluate serif font stack for headers
Status: NEW
Product: MediaWiki skins
Classification: Unclassified
Vector (Other open bugs)
unspecified
All All
: Low enhancement
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-09-24 16:30 UTC by Isarra
Modified: 2014-10-04 06:48 UTC (History)
7 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Isarra 2014-09-24 16:30:20 UTC
In vector, the h1 and h2 use serif fonts (everything else is sans-serif). Unfortunately the font stack used results in a highly inconsistent user experience across different browsers, due to also affecting the visibility and or relative sizes of the headers.

The stack is thus: @content-heading-font-family: "Linux Libertine", Georgia, Times, serif;

Linux Libertine: Ideal font according to the current design. Relatively small, heavy serif font. Installed by default on pretty much no platforms.

Georgia: Relatively large, light serif font, when compared to Linux Libertine. Incompatible with some languages, also results in legibility issues due to strange rules for some character combinations. Installed by default on windows and mac(?).

Times: Somewhat generic fallback. Tries to go for a 'times' style serif or something. No different effect than 'serif' on most platforms.

serif: Generic fallback. Results in any number of different fonts, from DejaVu serif (which is downright ugly especially at larger sizes) to Times New Roman (which is smaller and lighter than Georgia).


Headers need to stand out in order to be effective, and the relative small sizes and lightness of some of these, especially when combined with relatively large sans-serif fonts in other headers/content text, limits this effectiveness on some platforms.

If the font delivered could be standardised (probably to the default, Linux Libertine), this could help to address many of the inconsistency issues. However, if core support for webfonts is not yet sufficient to handle this, is this font stack really appropriate at present given its inherent instability?
Comment 1 Jared Zimmerman (WMF) 2014-09-24 18:20:58 UTC
While we'd love to deliver a web font, I don't think we have the resources to fully test this for compatibility and performance at this time, but I think a lot of other people (including myself) think this would be a great idea to investigate, when time and resources allow
Comment 2 Erwin Dokter 2014-10-04 06:48:44 UTC
See also https://www.mediawiki.org/wiki/Talk:Typography_refresh#Header_fontstack where I propose a Times based font stack.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links