Firefox is undergoing a gradual overhaul of its entire architecture that
will bring dramatic performance, stability, and security improvements.
https://wiki.mozilla.org/Quantum

During this process, Mozilla's work on the Rust language and technologies
being developed presently under the Servo engine are being systematically
integrated to replace existing Firefox components. One of the trade-offs in
this process, is that the XUL customization framework that has been
historically used to allow for near-unlimited customization is being
retired, because it is a significant architectural roadblock to
multithreaded and multiprocess Firefox and a significant source of
performance impacts. The successor, WebExtensions is very similar to Chrome
extensions, and more limited, but I recall there's ongoing work to make it
more functional. I'm not sure of the degree of theming that will be
possible though.








On Mon, Apr 24, 2017 at 7:01 PM, Paul Kosinski <[email protected]> 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?
> _______________________________________________
> 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"
>
_______________________________________________
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"

Reply via email to