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

Mulongo oyo etiyamaki na archive. Tuna motuna mosusu soki osengeli na lisalisi

autoconfig use of profile-after-change

  • 1 eyano
  • 1 eza na nkokoso oyo
  • 1 view
  • Eyano yasuka ya 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?

All Replies (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.