Firefox loses yet another high profile add-on author: Quicksaver quits

[Batu69]

The respected Firefox add-on developer Quicksaver announced yesterday that he won't update any of his extensions anymore because of Mozilla's decision to move to WebExtensions exclusively.

 

Quicksaver, responsible for add-ons such as Tab Groups, OmniSidebar, FindBar Tweak, Beyond Australis and Puzzle Bars, had four of his five add-ons for Firefox featured by Mozilla in the past.

 

If you open any of the author's add-on pages on the Mozilla Add-ons repository, you will notice an important announcement on the page.

 

It reads: IMPORTANT: The add-on will not receive any more updates and will stop working by next November with Firefox 57.

The add-ons won't work anymore when Firefox 57 comes along (the first version of the browser said to be WebExtensions exlusive).

Firefox add-on author Quicksaver quits because of WebExtensions

 

The author's add-ons are:

• Beyond Australis -- The add-on added tweaks and new features to Firefox's then new browser UI theme Australis. Has more than 40,000 users, 330 user reviews, and a five star rating.
• FindBar Tweak -- Improves Firefox's on-page find functionality, for instance by making it search on all open tabs, or moving the results to a different location. Has more than 31,000 users, 302 user reviews, and a five star rating. Our FindBar Tweak review.
• OmniSidebar -- Makes the sidebar of Firefox more accessible and powerful. More than 109,000 users, 111 user reviews, a five star rating. Our Omnibar review.
• Puzzle Bars -- Enables you to place add-on buttons and other icons in the browser window exactly like you want them to. More than 4000 users, 66 user reviews, a five star rating. Our Puzzle Bars Review
• Tab Groups -- This brought back the Firefox Panorama / Tab Groups functionality that Mozilla removed from the browser some time ago. Has more than 111,000 users, 548 user reviews and a five star rating. Our Tab Groups review.

Quicksaver posted an explanation on his website that reveals why he made the decision to stop add-on development.

There are several reasons, but the core reason given is that at least four of his five add-ons rely heavily on functionality that will either not be provided by WebExtensions, or would require him to rewrite the extension almost completely.

However, manipulation of the browser window's interface and functionality will be extremely limited by definition, and even if it wasn't, the implementation of such abilities is nearly impossible to achieve in WebExtensions.

According to the explanation, Quicksaver was in contact with Mozilla to find a way to keep his extensions alive, but failed ultimately.

I have fought for keeping the current system working together with WebExtensions, not only to keep all of my add-ons alive, but also because I believe a can-do-whatever-you-want extension system like exists today is the best quality Firefox has over other browsers. Unfortunately I've failed to convince them of this, as have they failed to convince me of the benefits they expect to achieve with a WebExtensions-only system.

Another point that the author makes is that he went through the ordeal of rewritting his extensions not too long ago. When Mozilla announced multi-process Firefox, he rewrote the extensions to make them compatible with it.

To sum it up:

• WebExtensions won't support the functionality required for porting at least three of the five extensions over.
• The other extensions would require huge effort on the author's part as code needs to be rewritten to a large extent.
• Mozilla is dead on track to throw Firefox's old add-on system out of the window, and seems inclined to accept any fallout this may cause.

Closing Words

It was clear from the beginning that the move to WebExtensions will leave add-ons and authors behind. While Mozilla plans to make WebExtensions in Firefox more powerful than in Chrome, they will never be as powerful as Firefox's current add-on system.

 

Quicksaver is not the only author who announced that he will stop working on add-ons for Firefox. Add-ons like New Tab Tools, Classic Theme Restorer, Tree Style Tabs, Open With, DownThem All, KeeFox and many others are likely also not going to make the cut.

 

Firefox will lose good functionality because of this, something that probably won't ever come back once the move to WebExtensions is finalized.

Mozilla Firefox will gain support for the bulk of Chrome extensions, and while that is a good thing, they cannot fill the gap that the move to WebExtensions will cause.

 

Mozilla's timing on this one is off in my opinion. The organization could keep the old add-on system alive, at least for a bit longer, until WebExtensions are more capable. The whole ordeal feels rushed to me.

 

Article source

[pc71520]

Will more add-on Developers follow?

[DKT27]

It's sad to see this happen. Mozilla has to delay this, the marketshare is not going anywhere.

 

While I can completely understand the need to let go of the current addons as this is what is keeping Firefox behind in speed, I think Mozilla needs to find a way to fix this issue.

 

I personally feel that if this indeed is such a big problem, then Mozilla should release another version of Firefox, something named Firefox WebX, where the new addons are allowed then see if people like it or use it.

[danielson]

@DKT27 - i "liked/thanks" your post but with Firefox, it doesn't seem to let me know if it does or not.

 

What about if Mozilla setup an extension that could check if another one is kosher or not?

I'm sure other devs would be glad to contribute.

They're doing a check by default within the browser itself for compatibility, why not push it a step further?

[DKT27]

2 hours ago, danielson said:

@DKT27 - i "liked/thanks" your post but with Firefox, it doesn't seem to let me know if it does or not.

 

What about if Mozilla setup an extension that could check if another one is kosher or not?

I'm sure other devs would be glad to contribute.

They're doing a check by default within the browser itself for compatibility, why not push it a step further?

 

You probably are using the HTTPS version of the forums, it's broken, use the non-HTTPS version instead.

 

A lot of options can be tried, they just need to look into it.

[danielson]

In line with what pc71520 was wondering here, perhaps more 1st class devs should follow suite.

Since Mozilla doesn't seem to listen to its users, perhaps a massive move on behalf of the devs would get some of their attention?