644883 - Web Font changes by the Chinese version of firefox's components

Status: RESOLVED INVALID

(Websites :: www.mozillaonline.com, defect)

Description

[s5s5]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.151 Safari/534.16
Build Identifier: 

Chinese version of the firefox is download from http://firefox.com.cn.
It will guide the user during installation to install some components.
Which has a component called "字体设置", it will change the browser's default font into "Microsoft YaHei".
The font changes will lead to bad is I made some websites, such as:http://www.misuisui.com/weblog/wp-content/uploads/2011/03/qzoneshop.png .
Why download the firefox from China and the United States not the same download of firefox?
You must stop the Chinese site that installed the component behavior.
This behavior is very bad, unpleasant.
Thank you

Reproducible: Always

Comment 1

[japandi]

I noticed this behavior likely stems from font preferences being overridden at install time in a localized distribution. Is there any existing mechanism in Firefox to surface such overrides to users or developers, or would a DevTools or settings-level visibility feature be a more appropriate direction to explore?

Comment 2

[:Gijs (he/him)]

(In reply to japandi from comment #1)

I noticed this behavior likely stems from font preferences being overridden at install time in a localized distribution. Is there any existing mechanism in Firefox to surface such overrides to users or developers, or would a DevTools or settings-level visibility feature be a more appropriate direction to explore?

about:policies exists for enterprise policies. I'm not sure what you mean by "localized distribution". The older "Chinese version" of Firefox that is referenced by this (15 year old!!) report no longer exists, but it did a bunch of stuff other than just localization (or enterprise policies).

We are actually removing localized preferences (bug 1760013) but in a way that's perhaps an implementation detail.

If you think there is still a problem, 15 years later, it would be helpful to have some more details of what you're seeing that's problematic and why you think "surface this more obviously to users" is the right solution.

Comment 3

[japandi]

never mind, I believe this is over 15 years old and is no longer an issue, as about:policies handles it. should this bug be closed as WONTFIX ?