Currently, Lato is being pulled from Google Font's server, and in Refreshed/refreshed/main.css - This should be defined instead in MediaWiki:Refreshed.css or MediaWiki:Refreshed-font (but preferrably the former)
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | MtMNC | T134669 Make Refreshed skin less specific to Brickimedia | |||
| Resolved | MtMNC | T142157 Make Refreshed less-specific to Brickimedia: Custom font for skin should be definable on wiki instead of the repo |
Event Timeline
Comment Actions
I support this. Should the default header font-family be the same as the current body scheme ("Helvetica Neue","Helvetica","Arial",sans-serif) or should it match Vector's header ("Linux Libertine",Georgia,Times,serif)?
Comment Actions
I personally disagree with the order of the font stacking, but I'd go with a sans-serif font stack. Here's a little comparison for these based on websafe compatibility across operating systems:
- http://www.cssfontstack.com/Arial - Windows: 99.84% / Mac: 98.74%" (balanced)
- http://www.cssfontstack.com/Helvetica Windows: 7.34% / Mac: 100%" (wayyy unbalanced)
font-family: Arial, "Helvetica Neue", "Helvetica", sans-serif;
How about this one above? :D
Comment Actions
Oh yeah that'd be fine. That stack was based on the one planned for the MediaWiki typography refresh, but in the end it wasn't used and plain old sans-serif was used instead.
Comment Actions
Would it not make sense to ship the skin with a simple font-family: sans-serif and not worry about different font face compatibility across platforms? That leaves font choice entirely up to the end user which could be a good or a bad thing.