On Thu, Nov 02, 2017 at 01:06:09AM +0100, Jörg Knobloch wrote:
On 02/11/2017 00:41, Nicholas Nethercote wrote:
1) Remove the defaults/preferences directory support for extensions. This
is a feature that was used by legacy extensions but is not used by
WebExtensions.
Is that the facility that legacy extensions can have
defaults/preferences/defaults.js to declare their preferences?
In Thunderbird we're trying to keep legacy extensions working, currently
by having |ac_add_options "MOZ_ALLOW_LEGACY_EXTENSIONS=1"| in the
mozconfigs.
So are the components legacy extensions rely on slowly dismantled? So some
will keep working and some will stop working?
Yes. The components that non-bootstrapped add-ons rely on,
anyway.
If so, what is the replacement? Setting up the preference in JS on the fly
in the add-on?
Yes.
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
