(see ETA at end: 57+ nightlys and "unbranded" betas will run legacy add-ons; "branded" betas and release candidates won't, unless "Signed by Mozilla internally")
I haven't tracked down when or why this change was made, if it was ever formally announced, and so on, but according to an older blog post I found tonight, legacy add-ons will still work in 57+ (if I'm reading things right; hopefully I am). To keep this comment brief, I quote the Mozilla post in question here: https://marahmarie.dreamwidth.org/358969.html
It's very confusing to find out when/why the decision was made when the blog post I'm quoting just says Update at the top, twice, but doesn't give a precise date/dates. Talk about not wanting you to know.
Also/also, there is supposed to be some sort of functionality in the add-on manager to sort of IFTTT the legacy add-ons (a recommendation engine Mozilla created to help those of us whose fave add-ons are sunsetting entirely, at least for now).
But for one, I can't find it and for another, I think it's kind of a slap in the face to private add-on devs who can't update fast enough owing to Mozilla's lacking the APIs for them to refer those add-on users to other (mostly lesser) add-ons, so I don't know....I just think they're going about many parts of this all wrong.
ETA: just did another search and came up with this: https://wiki.mozilla.org/Add-ons/Firefox57 which indicates - weirdly enough - that once 57's released, legacy add-ons won't be compatible in the "branded" betas or release versions (unless "Signed by Mozilla internally"), but will be compatible in nightlys and "unbranded" betas going forward, which is sort of the exact opposite behavior I would expect, but OK then, very well *sigh*.
Will add an ETA to my own post soon to reflect this added...
no subject
I haven't tracked down when or why this change was made, if it was ever formally announced, and so on, but according to an older blog post I found tonight, legacy add-ons will still work in 57+ (if I'm reading things right; hopefully I am). To keep this comment brief, I quote the Mozilla post in question here: https://marahmarie.dreamwidth.org/358969.html
It's very confusing to find out when/why the decision was made when the blog post I'm quoting just says Update at the top, twice, but doesn't give a precise date/dates. Talk about not wanting you to know.
Also/also, there is supposed to be some sort of functionality in the add-on manager to sort of IFTTT the legacy add-ons (a recommendation engine Mozilla created to help those of us whose fave add-ons are sunsetting entirely, at least for now).
But for one, I can't find it and for another, I think it's kind of a slap in the face to private add-on devs who can't update fast enough owing to Mozilla's lacking the APIs for them to refer those add-on users to other (mostly lesser) add-ons, so I don't know....I just think they're going about many parts of this all wrong.
ETA: just did another search and came up with this: https://wiki.mozilla.org/Add-ons/Firefox57 which indicates - weirdly enough - that once 57's released, legacy add-ons won't be compatible in the "branded" betas or release versions (unless "Signed by Mozilla internally"), but will be compatible in nightlys and "unbranded" betas going forward, which is sort of the exact opposite behavior I would expect, but OK then, very well *sigh*.
Will add an ETA to my own post soon to reflect thisadded...