Closed
Bug 1038808
Opened 11 years ago
Closed 11 years ago
backout the fira mono font
Categories
(bugzilla.mozilla.org Graveyard :: Sandstone/Mozilla Skin, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: glob, Assigned: glob)
Details
following significant negative feedback about the readability of comments with the fira's mono font, we should backout that change (but continue to use fira for the rest of the UI).
To ssh://gitolite3@git.mozilla.org/webtools/bmo/bugzilla.git
3e8a6b2..ccd31ef master -> master
readability feedback includes:
- the "r" is too similar to a dot-less "i"
- * and + are too similar
- the kerning is very weird
- i have to increase my font size to 150% to read comments
i'll chase up these issues with the visual design team; i'd love to see fira-mono re-enabled on bmo at some stage.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Comment 2•11 years ago
|
||
Just curious, is there a way to allow users to set their own font instead of system-wide?
Comment 3•11 years ago
|
||
(In reply to Lukas Blakk [:lsblakk] from comment #2)
> Just curious, is there a way to allow users to set their own font instead of
> system-wide?
Not built in to Bugzilla. There are various Firefox hacks that can be done.
http://superuser.com/questions/527774/replace-fonts-in-firefox-on-only-certain-websites-and-only-certain-fonts
dkl
Comment 4•11 years ago
|
||
(In reply to Lukas Blakk [:lsblakk] from comment #2)
> Just curious, is there a way to allow users to set their own font instead of
> system-wide?
Added to BzDeck's TODO list! https://github.com/kyoshino/bzdeck/issues/115
(In reply to Lukas Blakk [:lsblakk] from comment #2)
> Just curious, is there a way to allow users to set their own font instead of
> system-wide?
no, but it's possible for us to provide alternative fonts for the skins.
we already do that for dusk, i've filed bug 1039146 for providing an opensans alternative for the mozilla skin.
Updated•7 years ago
|
Product: bugzilla.mozilla.org → bugzilla.mozilla.org Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•