Closed
Bug 1059112
Opened 10 years ago
Closed 10 years ago
MozTT font-family URL is incorrect, causing large text in the edit textarea
Categories
(Websites :: wiki.mozilla.org, defect)
Websites
wiki.mozilla.org
Tracking
(Not tracked)
RESOLVED
FIXED
2014-Q3
People
(Reporter: glob, Unassigned)
References
Details
(Whiteboard: [dev=2014-09-25][prod=2014-09-25])
Comment hidden (typo) |
oops; typo in first comment: corrected version: when editing a page, the font-size of the textarea is massive in comparison with normal <pre> text. the url for downloading the MozTT font-family is 403'ing: https://developer.cdn.mozilla.net/media/redesign/fonts/MozTT-regular-webfont.woff this triggers bug 175415, which results in a monospace font being rendered with a sans-serif size (on my system it's 16px instead of 13px).
Comment 3•10 years ago
|
||
Looks like the font has either been removed from the CDN or relocated. Anyone else have a working url for MozTT? Perhaps we should just replace MozTT and Open Sans with Fira? Anyone know if those have been posted to one of our CDNs?
Comment 4•10 years ago
|
||
It's probably unwise to use a random location that happens to contain the font you want - that puts you at the mercy of whoever owns that URL path, just as happened with the devmo link.
Comment 5•10 years ago
|
||
Agreed. I'm working on tracking down whether or not there will be a canonical place to host our identity's fonts, which is why I asked if anyone know whether or not they were already being hosted on one of our CDNs.
Comment 6•10 years ago
|
||
We're now loading Fira font family directly from Mozilla Wiki and I've updated the stylesheets to use Fira Mono instead of MozTT: https://wiki.mozilla.org/index.php?title=MediaWiki:Vector.css&oldid=1018339 This should be fixed now. You might need to shift-refresh to see the changes.
Status: NEW → RESOLVED
Closed: 10 years ago
OS: Mac OS X → All
Hardware: x86 → All
Resolution: --- → FIXED
Whiteboard: [dev=2014-09-25][prod=2014-09-25]
Target Milestone: --- → 2014-Q3
You need to log in
before you can comment on or make changes to this bug.