Open Bug 775797 Opened 14 years ago Updated 4 years ago

Fonts from prefs for Western script used instead of fonts for Hebrew script on some sites

Categories

(Core :: Layout: Text and Fonts, defect)

Product:
Core
Component:
Layout: Text and Fonts
Platform:
x86
Windows 7
Type:
defect

Tracking

()

People

(Reporter: smontagu, Unassigned)

References

Details

(Keywords: regression)

This was reported on http://www.mozilla.org.il/board/viewtopic.php?f=9&t=11067 (in Hebrew). Steps to reproduce: In fonts prefs, UNset the option "Allow sites to use other fonts ..." Go to http://sharetw.info/ Expected results: use the fonts from the Hebrew font prefs. Actual results: the fonts from the Western font prefs are used. Note that the site has on the one hand |lang="en"| and on the other hand |Content-Type: text/html;charset=WINDOWS-1255| Apparently in earlier versions this caused us to use the fonts for Hebrew, but this changed.
Probably the work in bug 524107 and bug 547267, but I think that's a good thing.
Simon, I think you need to add more steps here and be more specific about the differences you see (i.e. point out specific fonts in use on the page that changed from earlier versions). One immediate question is *which* previous version renders differently? I created a new profile, unchecked the "allow sites to use other fonts", and set the default fonts for Western to Verdana. Using this profile, the sharetw.info page renders pretty much the same from FF12 to trunk. A reduced testcase attached to this bug would be ideal since that site has dynamic content in it.
(In reply to John Daggett (:jtd) from comment #2) > One immediate question is *which* previous version renders differently? I > created a new profile, unchecked the "allow sites to use other fonts", and > set the default fonts for Western to Verdana. Using this profile, the > sharetw.info page renders pretty much the same from FF12 to trunk. I haven't been able to reproduce this bug myself and am only reporting the symptoms at second hand, but the user who originally reported it set the default fonts for Hebrew to Tahoma, and (AFAIK) didn't change the default fonts for Western. He also says that he sees the bug in FF13 but not in FF11. Obviously we need a saner regression range to move forward.
I just tried this on Win7 and AFAICT the preference to *not* allow pages to use their own fonts (i.e. clearing the checkbox in Options) seems to be broken in both FF11 and FF12 - the http://sharetw.info page remains stubbornly in Arial (as per its CSS), regardless of changes to either the Western or Hebrew font prefs - but works as expected in FF13. I'm not clear why the behavior changed between 12 and 13, but as of now I think something actually got _fixed_; however, it may make it more likely that people see unexpected results due to poor language tagging.
Ah - no - it's more subtle than that. On FF12 (at least), on both Win7 and MacOS, it's not actually using Arial from the sharetw.info page's CSS. What I'm seeing is that with "allow sites to choose their own fonts" disabled, the page is using the *sans-serif* font from the Western font prefs, even though I've got Proportional: Serif selected. OTOH, FF13 uses the *serif* font from the Western prefs, as expected. So it kind of looks as though FF12 was ignoring the actual family names from the CSS, but still respecting the generic "sans-serif" in the CSS list; FF13 ignores even this and just uses "serif" from the Western prefs. Are CSS generics supposed to be ignored when "allow sites to choose..." is disabled, or are we supposed to ignore actual family names but still use the generics?
(In reply to Jonathan Kew (:jfkthame) from comment #5) > Are CSS generics supposed to be ignored when "allow sites to choose..." is > disabled, or are we supposed to ignore actual family names but still use the > generics? Part of the font group setup logic automatically appends "serif" to the end of the font list as I recall.
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.