Windows 10 已于2025年10月14日停止支持。如果您正在使用 Windows 10,参见 这篇文章

Windows 10 reached EOS (end of support) on October 14, 2025. If you are on Windows 10, see this article.

搜索 | 用户支持

防范以用户支持为名的诈骗。我们绝对不会要求您拨打电话或发送短信,及提供任何个人信息。请使用“举报滥用”选项报告涉及违规的行为。

详细了解

What happened to firefox-l10n.js in Firefox 149?

  • 3 个回答
  • 0 人有此问题
  • 126 次查看
  • 最后回复者为 TyDraniu
  • Open

With the latest Firefox 149, the firefox-l10n.js in omni.ja seems to be gone? its normally located in \defaults\preferences\ the file is now completely missing in the omni.ja is it now named differently or is it migrated into another file? normally i edit the file and add for our deployment: pref("network.proxy.type", 0);

With the latest Firefox 149, the firefox-l10n.js in omni.ja seems to be gone? its normally located in \defaults\preferences\ the file is now completely missing in the omni.ja is it now named differently or is it migrated into another file? normally i edit the file and add for our deployment: pref("network.proxy.type", 0);

所有回复 (3)

Hi,

This file has been removed in v149. Please see this bug.

I'm not an expert in this, but why won't you set up a policy instead? Also, are you using Enterprise?

the policy locks the setting. but i dont want it to be locked. i only want to set it once. and if the user needs to change it later, he should have the rights to do it. with my explained way via firefox-l10n.js this was never a problem.

  1. Why not use user.js/prefs.js?
  2. Policy doesn't lock it, there's Locked parameter you can set to 0, see https://mozilla.github.io/policy-templates/#proxy
  3. Editing omni.ja should be avoided.
我要提问

您需要登录才能回复。如果您还没账号,可以提出新问题