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

Avatar for Username

Tìm kiếm hỗ trợ

Tránh các lừa đảo về hỗ trợ. Chúng tôi sẽ không bao giờ yêu cầu bạn gọi hoặc nhắn tin đến số điện thoại hoặc chia sẻ thông tin cá nhân. Vui lòng báo cáo hoạt động đáng ngờ bằng cách sử dụng tùy chọn "Báo cáo lạm dụng".

Tìm hiểu thêm
Open

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

Firefox Tùy biến
TyDraniu đã trả lời
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);

Tất cả các câu trả lời (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 Người tạo câu hỏi

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.
Đặt một câu hỏi

Bạn phải đăng nhập vào tài khoản của bạn để trả lời bài viết. Vui lòng bắt đầu một câu hỏi mới, nếu bạn chưa có tài khoản.