is there are a particular technical reason, why this is targetting 52 and upwards? i'm asking because we've also seen a couple of OSX 10.6-10.8 users stranded on firefox 48 [1] inquiring what's the remedy for them in support channels. if there are no technical hurdles, extending this system addon to versions 48 upwards would therefore be appreciated. (incidentally firefox 48 was also the first version where `xpinstall.signatures.required` didn't take effect any longer and affected users don't have an easy workaround) [1] https://support.mozilla.org/en-US/kb/firefox-osx [2] https://wiki.mozilla.org/Add-ons/Extension_Signing#Timeline
Bug 1549604 Comment 55 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
is there are a particular technical reason, why this is targetting 52 and upwards? i'm asking because we've also seen a couple of OSX 10.6-10.8 users stranded on firefox 48 [1] inquiring what's the remedy for them in support channels. if there are no technical hurdles, extending this system addon to versions 48 upwards would therefore be appreciated. (incidentally firefox 48 was also the first version where `xpinstall.signatures.required` didn't take effect any longer and affected users don't have an easy workaround [2]) [1] https://support.mozilla.org/en-US/kb/firefox-osx [2] https://wiki.mozilla.org/Add-ons/Extension_Signing#Timeline