On Tue, Oct 17, 2017 at 1:33 AM, James Hogarth <james.hogarth@xxxxxxxxx> wrote:
And even if we hypothetically forked Firefox (as that is what it would be) to add legacy extension capability back it would mark a significant divergence with upstream and I'm not sure if addons.mozilla.org could even be used then anyway as it'd detect FF57 and state that older extensions are not supported. That doesn't even go into the legal situation as to whether we could even call it Firefox with such divergence (remember Iceweasel?) ... there's a reason there's a whitelist on the Firefox packages for build permissions after all.And how long would you want FF packagers to maintain such a patchset for? Even the next ESR will drop legacy extensions.
Yup! It's a non-starter. Mozilla knows exactly what they are doing - and have made their decision.
_______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
