Mozilla Will Deprecate XUL Add-ons Before the End of 2017

Artem Tashkinov writes: Mozilla has published a plan of add-ons deprecation in future Firefox releases. Firefox 53 will run in multi process mode by default for all users with some exceptions. Most add ons will continue to function, however certain add ons have already ceased to function because they don't expect multi user mode under the hood. Firefox 54-56 will introduce even more changes which will ultimately break even more addons. Firefox 57, which will be preliminarily released on the 28th of Novermber, 2017, will only run WebExtensions: which means no XUL (overlay) add ons, no bootstrapped extensions, no SDK extensions and no Embedded WebExtensions. In other words by this date the chromification of Firefox will have been completed. If you depend on XUL add ons your only choice past this date will be Pale Moon.

Comments

Great.

[Anonymous Coward]

Why bother using this bloated browser when it drops support for the incredible addon library it's accumulated over the years? Without customization, what exactly does Firefox offer over Chrome?

Re:Great.

[K. S. Kyosuke]

Exactly. "If it's successful and it works, remove the feature" seems to be rather popular these days.

Re:Great.

[higuita]

Because current add-on design do not work with multi-process!!

They are not ending the add-on, they must be migrated to the new API. Sadly many add-on are abandoned and will not be migrated. Others will not be allowed to do some functions, almost all of then must be rewritten. But the current add-on have fatal flaws and are doomed sooner or later.

There are several problems with the current^WOLD add-on layer
1- Old add-on have too much access to the firefox internals (security, memory leaks and performance problems)
2- Old add-ons do not know how to work with multi-process and mozilla had to simulate a pool+lock for then to work (big lock, performance problems)
3- Migrating code from Servo to Geko would break many add-on unless there are many compatibility layers (performance and code maintenance problems)

Solutions:
1-They could swap unsafe parts slowly and break many add-on on each release, forcing a slow and never ending add-on update cycle. It is much easier to just swap the API and warn that everyone must rewrite.
2-Add-ons need to be fixed or else the browser will not really use the multi-process well and worse, may be even slower because of the big lock. If they remove the compatilbity layer, add-on stop working, but postponing the removal will keep the browser slower too and the add-on may never be updated (multi-process is already a several years project and all add-ons where flagged to be updated, but many are just abandoned). So wait more is not a solution, they need to be rewrite
3-No one wants layers over layers, it is a maintenance hell, specially because the add-on have access to almost everything. Migrating to a simpler API make mozilla job much easier, firefox safer. Add-on will have to be rebuild and developers need to learn a new API. They will also be unable to do some things they can right now, but on the good side, it will much easier to port add-on between chrome and firefox and the add-on can be run in separated process, so bad add-on will be easier to stop and control.

Yes, i too would like to keep all the add-ons, but between a fast browser with fewer add-ons and a slow one with many outdated add-ons, i prefer the first one. You can not complain about firefox being slow and also complain about keeping old add-ons. To fix one, you need to fix the other too! and you can not delay this, market share is shrinking due firefox being slower.

They were making changes slowly, as they were mostly doing the last few years, and try to not break the add-ons, but you can not postpone a big internal change forever and now it is time to drop some old features, like NPAPI plugins and the old add-on interface

What i hope is that mozilla is now more open to some features, as some features will be blocked to add-ons, mozilla need to be more flexible on certain features. The google design model ("only allow features that at least 80% of people use") is bad for firefox, as many of the users of firefox are the 20% of excluded people in chrome

Re:Great.

[Anonymous Coward]

Speed is NOT the problem with Firefox. The problem is that the UI keeps getting worse.

I have to have addons for putting a status bar back at the bottom, I have to have addons for putting the window title back at the top. I don't want the preferences in a tab, I want them in a window. I have zero interest in reading lists, whatever the fuck "Pocket" is, or any of the other new shit that keeps showing up and not used by anybody.

It pisses me off that plugins were intentionally broken. It pisses me off that the first thing I have to do upon install is remove Yahoo as a search engine. I usually use a Mac, but when I'm having to use Windoze, before I can do anything else, I have to turn the menu bar back on - it should never be off, it shouldn't even be possible to turn it off.

I run four extensions that are critical: Classic Theme Restorer, Status 4 Evar, Adblock Plus, and NoScript. I also typically install a video download extension, because YouTube sucks.

If those extensions break, I'll have to drop back to a LTS release and hope somebody forks Firefox.

Dump the new API, then you won't have layers upon layers, just the one that works.

Re:Great.

[0111 1110]

Yes, i too would like to keep all the add-ons, but between a fast browser with fewer add-ons and a slow one with many outdated add-ons, i prefer the first one.

Doesn't a fast browser with fewer addons basically describe Google Chrome? Why don't you just switch to that if speed trumps customization for you? Do you really think the mozdevs can compete with the massive GoogleCorp at what they do best? You think they are going to outGoogle Google?

You can not complain about firefox being slow and also complain about keeping old add-ons.

I haven't seen a lot of people complaining about speed for any browser. I don't think speed is much of an issue for browsers. They have been fast enough for a very long time. Trying to make them faster is fixing a nonproblem. Finding a browser that will do what you want it to do if you want more than what Chrome can do otoh...that's about to be nontrivial.

Pale Moon is very nice

[Doke]

I've been using Pale Moon for a couple years. I hated when Firefox went to the Australis, chrome clone, interface. I hated when Firefox kept deleting features, especially preferences. Pale Moon is lighter, faster, more customizable, and pays more attention to security ideas. They were the first to deal with html5 canvas fingerprinting.

On the down side, I do occasionally find a site that won't work. I'm not entirely sure if it's Pale Moon, or my combination of script and ad blockers. It's usually a fluff entertainment site, and I don't care enough to turn them all off, or fire up chrome.

An obviously bad move

[iampiti]

The justification they've given for removing classic extension support is that they depend too much on the internals of Firefox, for the same reason they also said they're a security risk.
They are valid technical reasons. Most people would agree that making extensions use a stable API decoupled from the browser's internals is a good thing for stability and compatibility in the long run.
But, and this is a very big but, that means many popular current extensions can't just be made to work with the new APIs. Also, the ones that can be adapted will probably need a good amount of work. The result is that many extension developers have said they will abandon their extensions.
Also, since those powerful extensions are one of the reasons many people keep using Firefox that will surely suppose a big hit on their maket share and that's the last thing Firefox needs.
Their stated mission is to fight to keep the web open, if nobody uses their browser they'll have no money and no influence and hence they can't fulfill their mission.
I know this must've been a hard decision to make at Mozilla but I feel it's not the right one.

Actual Post

[gQuigs]

https://blog.mozilla.org/addon...

In other words...

[Dracos]

This year, Mozilla Will Remove the #2 reason everyone started using Firefox in the first place.

Copying Chrome has been a bad strategy, and killing XUL is one of their worst decisions ever. I'm waiting for the announcement that Firefox will become a re-branded Chrome, like Opera. Yay for software monoculture!

Massive loss of capability.

[Gravis Zero]

The new WebExtensions API is capable of many things but there is going to be a lot of lost capabilities. There are some pages comparing the capabilities and you'll find WebExtensions is lacking in many areas.

WebExtensions versus XUL/XPCOM extensions - see "Services.jsm API" table.
WebExtensions versus Add-on SDK - see "Low-level APIs" table

I don't know if Firefox will recover from this kind of seismic shift in APIs. Let's just hope they were rarely utilized parts of the API or that they are currently developing new replacements for the parts that people loved.

Deletion disorder is a treatable mental condition

[WaffleMonster]

Some people honestly believe throwing shit and features in the trash because it aligns with their narrow opinions and agendas is a constructive activity. They are incapable or unwilling to accept the possibility of a reality beyond their narrow worldview.

From mass deletion of useful articles from Wikipedia to the bands of trolls constantly closing questions they don't understand on SO. From land of "developers" creating "API"s they constantly and willfully break and defecate (deprecate).. because why shouldn't everyone else be expected to constantly play semantic musical chairs to make *your* unorganized life marginally easier?

All of those who think taking settings away and denying user choice constitutes a better user experience or who truly believe everyone appreciates your nonsensical unproductive abstract notions of art that make software painful and unusable...There is a cure. You can be saved.

Avoid use of ALL computer INPUT device until end of days n ye shall be cured. ~ from Book of Krusteaz 12:10.