Important Notice: We're experiencing email notification issues. If you've posted a question in the community forums recently, please check your profile manually for responses while we're working to fix this.

On Monday the 3rd of March, around 5pm UTC (9am PT) users may experience a brief period of downtime while one of our underlying services is under maintenance.

ค้นหาฝ่ายสนับสนุน

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.

เรียนรู้เพิ่มเติม

autoconfig use of profile-after-change

  • 1 การตอบกลับ
  • 1 คนมีปัญหานี้
  • 1 ครั้งที่ดู
  • ตอบกลับล่าสุดโดย cor-el

more options

Before Firefox 60, the autoconfig file (.cfg file) could register an observer for "profile-after-change" (so as to change things such as the default search engine), like this:

   Components.utils.import("resource://gre/modules/Services.jsm");
   Services.obs.addObserver(observer, "profile-after-change", false);

This no longer works (the first line fails outright). Is there a new way to register such an observer in an autoconfig file?

Before Firefox 60, the autoconfig file (.cfg file) could register an observer for "profile-after-change" (so as to change things such as the default search engine), like this: Components.utils.import("resource://gre/modules/Services.jsm"); Services.obs.addObserver(observer, "profile-after-change", false); This no longer works (the first line fails outright). Is there a new way to register such an observer in an autoconfig file?

การตอบกลับทั้งหมด (1)

more options

If you check the Browser Console then you will likely notice a message that "Autoconfig is sandboxed by default" (bug 1479857).

A possible workaround for now is to add a line in the autoconfig.js file disable this feature.

  • pref("general.config.sandbox_enabled", false);

Note that this pref might be removed in future Firefox versions.