Mozilla to Support Chrome Extensions

Mozilla has begun to make a series of changes to Firefox browser that will transform a number of internal functions to operate similar to Google Chrome. While the browser will gain stability and security, it will come at the cost of becoming a resource hog.

The company has been working on a multi-process architecture, called Electrolysis, via which Firefox will start using separate process for each tab. It will be enabled within the next few months across all versions of Firefox.

Firefox will soon have a different process for each tab, just like Chrome

The feature will be launched tentatively as an opt-in in the beta channel on September 22nd, it will become the default setting by November 3rd followed by a release for the stable channel from December 15th onwards.

The new engine and technology will help improve security and stability but there is a cost to the use of this technology. Current Firefox add-ons can intertwine with the inner workings of the browser using the old API which allows advanced controls for the add-ons. This becomes difficult with the new technique as the add-ons will work in a separate process from the main Firefox browser, thus, lesser integration.

The new engine and API mean that some add-ons with deep browser integration would not work with newer versions of Firefox

Mozilla has developed a temporary solution for the time being which will allow old add-ons to function until the transition is completed. The result isn’t as snappy as the final solution and will be slow and lack advanced integration.

Mozilla will eventually deactivate old add-ons that work on it. The deprecation will be carried out six months after the Electrolysis (process-per-tab) is launched which means June 2016 and will be completely removed from Mozilla Store in December 2016. After that addons that have not updated to the newer API will be removed by June 2017.

The usage of WebExtensions API means that Chrome extensions would work on Mozilla as well

Mozilla will implement WebExtensions API to replace the old one. This is based on the same technologies as the API in Chrome and Opera. Edge has been announced to support Chrome extensions as well. Firefox will be entering the club too, though, the extensions will be downloaded using Mozilla Store. This will be done to sign the add-ons and mark them secure before the users use them.

Digital signatures will be forced started version 42 (November 3rd) for the current extensions as well. Version 43 will introduce a separate process for tab content with deeper changes in tow. This marks Firefox’s historic entry to the multi-process era and also means that the Firefox might be leaving the extensive add-ons support that it has been famous for.

Source: ArsTechnica

He is the Editor-in-Chief at ProPakistani. Reach out at aadil.s[at]propakistani.pk


  • Bad, firefox will now eat ram just like chrome. Firefox uses threads for each tab thats why i was shifted from chrome to firefox. But now firefox will also use process for each tab, which is a bad thing. Although it will speed up but will use more ram

  • my 4GB RAM is always full when in Chrome so i switched to FireFox, looks like end of story next year of FireFox also. Laptop timing decreases way too much on Chrome and also Chromse install size is 5gb in my C Drive what the hell man.

  • Ltd feature videos

    Watch more at LTD

    close
    >