If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

firefox 9 doesn't handle the css font stack properly




6 years ago
6 years ago


(Reporter: dan, Unassigned)


9 Branch

Firefox Tracking Flags

(Not tracked)




6 years ago
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:9.0.1) Gecko/20100101 Firefox/9.0.1
Build ID: 20111222095143

Steps to reproduce:

visit a web site.

See http://usadancerichmond.org/test/ff9test.html
Also see this post in the Firefox help forum: https://support.mozilla.org/en-US/questions/907589
And this blog posting: http://krakrjak.blogspot.com/2012/01/firefox-901-font-css-bug.html

Actual results:

When ff 9 doesn't find the first font in the stack it defaults to one of it's own instead of cascading through the stack. 

Expected results:

It should cascade through the fonts until it finds one that works, not just substitute one of its own. Firefox 8.01 worked correctly, as do Chromium and Opera.

Comment 1

6 years ago
This bug is affecting many internal sites at my company.  This is a problem that I shouldn't have to work around because FireFox has decided to break CSS.

This seems to only affect 9.0.1 from my testing.  9.0 seems to have good behavior as do all previous versions of FireFox.
Zac, there was no change from 9.0 to 9.0.1 that could possibly have affected this.  Are you sure you don't see whatever you're seeing in 9.0.1 in 9.0?  Are the two using the same profile?

dan, which MediaWiki version is involved?
Component: General → Layout: Text
QA Contact: general → layout.fonts-and-text

Comment 3

6 years ago
Now that you mention it Boris, I'm not confident this bug doesn't affect 9.0.  By the time I got to test it I upgraded to 9.0.1 and the bug was present.  This very well could affect 9.0 also, does not affect lower versions.

I'm having issues with a modified version of the monobook theme from mediawiki 1.15.2.

Thank you for responding to this bug so quickly.  I wish someone would monitor the forums too.

Comment 4

6 years ago
I've done some more testing. It has something to do with the "clean" font. If it appears in the list before sans-serif it causes this behavior. The san-serif font must appear in the list and must be before "clean". Very odd.

In FF 8.0.1 this same thing happens, but only if clean is at the beginning of the font list.

What is it about the word "clean" that causes this?
Component: Layout: Text → General
You need to log in before you can comment on or make changes to this bug.