On 2017-04-24 at 16:01, Jorge Villalobos wrote: > On 4/24/17 1:01 PM, Paul Kosinski wrote: > >> I just installed Firefox ESR 52.1.0 to try it out and got a >> warning from Classic Theme Restorer that it will not work in ESR 59 >> et seq because the "XUL / XPCOM / legacy addon" support is being >> removed in 57. >> >> This would be a disaster from our point of view as the Classic >> Theme is the only way Firefox has a decent UI. (If we wanted >> Chrome, we'd use Chrome.) >> >> Does the removal of this support make the Classic Theme inherently >> impossible, or "just" a major new programming effort to update the >> CTR addon? > > It's inherently impossible for CTR to work as an add-on past 57. > Here are some posts with information on our plans: > > https://blog.mozilla.org/addons/2017/02/16/the-road-to-firefox-57-compatibility-milestones/ > https://blog.mozilla.org/addons/2016/11/23/add-ons-in-2017/
See also https://mail.mozilla.org/pipermail/dev-addons/2017-March/002675.html for explicit confirmation that they explicitly do not want to make it possible to do this sort of UI customization anymore. This is going to lose them users, and quite possibly put at least some of those users into a less secure situation (because those users stick with older, non-updated Firefox releases) - but the decision has apparently been made that the benefit, in maintainability and the opening up of future development paths, is worth that trade-off. -- The Wanderer The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man. -- George Bernard Shaw
signature.asc
Description: OpenPGP digital signature
_______________________________________________ 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"
