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

Vyhľadajte odpoveď

Vyhnite sa podvodom s podporou. Nikdy vás nebudeme žiadať, aby ste zavolali alebo poslali SMS na telefónne číslo alebo zdieľali osobné informácie. Nahláste prosím podozrivú aktivitu použitím voľby “Nahlásiť zneužitie”.

Ďalšie informácie

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

  • 3 odpovede
  • 0 má tento problém
  • 126 zobrazení
  • Posledná odpoveď od TyDraniu
  • Otvorené

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

Všetky odpovede (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.
Položiť otázku

Ak chcete odpovedať na príspevky, musíte sa prihlásiť do svojho účtu. Ak ešte nemáte účet, položte novú otázku.