Chrome extensions on Firefox are happening

Chrome-extensions-on-Firefox-aWhile multi-process support seems (and is) a good idea for anyone with a little bit of technical knowledge, it also means a complete overhaul of the entire browser’s architecture.

While previously Firefox used one single OS process to mix browser code, extensions, and Web content, with its Electrolysis project, Mozilla is moving extensions into their own process.

Mozilla is beginning to make a series of changes to Firefox that’ll make certain aspects of the browser operate a lot more like Chrome.


Mozilla has announced some big changes for Firefox and soon the browser will pick up more extensions (or add-ons) once exclusive to Chrome and Opera. Mozilla’s API extension will is compatible with on-demand web browers such as Chrome and Opera that run on Blink. “This modern and JavaScript-centric API has a number of advantages, including supporting multi-process browsers by default and mitigating the risk of misbehaving add-ons and malware”, Mozilla explained in a blog post.

To ensure third-party extensions provide customization without sacrificing security, performance or exposing users to malware, we will require all extensions to be validated and signed by Mozilla starting in Firefox 41, which will be released on September 22nd 2015. The company has also confirmed that add-ons that run on XPCOM and XUL languages will be slowly disapproved in the near future, and has been contemplating the exact plan of action to smoothen the process. However, the add-on model that arose naturally from these technologies is extremely permissive.

It’ll be interesting to see how this move will impact the Firefox add-on ecosystem. “This lack of modularity leads to many problems”. >more

Percento Cloud Servers