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

Avatar for Username

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

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

  • 3 replies
  • 0 have this problem
  • 7 views
  • Last reply by TyDraniu

Tynth
Tynth

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);

All Replies (3)

Denys
Denys
  • Moderator
  • Top 10 Contributor

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?

Tynth
Tynth Question owner

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.

TyDraniu
TyDraniu
  • Top 10 Contributor
  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.
Ask a question

You must log in to your account to reply to posts. Please start a new question, if you do not have an account yet.