Autoconfig had an original API for modifying preferences and doing other
things.
pref,
defaultPref,
lockPref,
unlockPref,
getPref,
clearPref,
displayError,
getenv,
This is the core API that will continue to be available.
At some point, Autoconfig was changed so that it could access any API in
Firefox. That is being removed on rapid release because it is being misused.
So things like adding certificates will not be available on rapid release.
Right now we've put this behind a preference to warn people of its removal.
Once things have settled down, we might look at adding additional APIs to
autoconfig if folks still need it, but our effort right now is on policy.
Mike Kaply
On Wed, Sep 19, 2018 at 2:01 AM, Luca Manganelli <
[email protected]> wrote:
> Il giorno mar 18 set 2018 alle ore 18:41 Mike Kaply
> <[email protected]> ha scritto:
> > This is because we have turned on Autconfig sandboxing by default on
> Firefox 62. From the release notes:
>
> So, what "Autoconfig sandboxing" means? In simple words?
> _______________________________________________
> Enterprise mailing list
> [email protected]
> https://mail.mozilla.org/listinfo/enterprise
>
> To unsubscribe from this list, please visit https://mail.mozilla.org/
> listinfo/enterprise or send an email to [email protected]
> with a subject of "unsubscribe"
>
_______________________________________________
Enterprise mailing list
[email protected]
https://mail.mozilla.org/listinfo/enterprise
To unsubscribe from this list, please visit
https://mail.mozilla.org/listinfo/enterprise or send an email to
[email protected] with a subject of "unsubscribe"
