veftown.blogg.se - Waterfox classic theme restorer

Waterfox classic theme restorer plus#

With APIs not ready yet, not even for testing, and uncertainty in regards to what WebExtensions will support, it is obvious that some add-on authors are not thrilled about the change.

Waterfox classic theme restorer plus#

What makes this even more problematic than it is, is that no one seems to know whether the capabilities that WebExtensions APIs will deliver once they are made available will be sufficient to port add-ons over.Ĭlassic Theme Restorer is but one of many add-ons, Tab Mix Plus is another, that faces this challenge. In fact, a whole category of add-ons, all that modify the browser UI, cannot be ported over because of missing APIs and the situation may be similar in other areas. This highlights one of the main concerns that the move to WebExtensions exclusivity raises: The APIs are not there yet. The end of the popular browser extension would bring the Australis design of Firefox to all users who relied on Classic Theme Restorer up until that point. Seems like its almost time to get used to another browser. We still have no way to change Firefox ui using WebExtensions and all my add-ons are about ui modifications. Now its real, CTR as we know it (and all my other Firefox add-ons), will be discontinued by the end of 2017. While Aris seems to have interest in porting over his extensions to WebExtensions, he notes that this is not possible right now. Classic Theme RestorerĪ recent post by Aris, developer of Classic Theme Restorer and several other popular add-ons such as Classic Toolbar Buttons, NewScrollbars, or GlassMyFox, suggests that Classic Theme Restorer may be dead by the end of 2017. Those are NoScript, Classic Theme Restorer, and Dictionary Switcher. I run three add-ons in my main Firefox work profile. While there is no guarantee that this is going to happen for all of them, the past has shown that Firefox add-on developers have picked up abandoned add-ons, and forked them to make them compatible with newer versions of the browser. Because WebExtensions will never support features needed by an add-on.Īny popular add-on under 1) may be forked or picked up by someone else.

The add-on author would like to port the add-on to WebExtensions, but cannot because the WebExtensions capabilities don't allow it yet (because of missing features).

This will happen for abandoned add-ons, but also if authors have no interest in porting their extensions.

The add-on author has not ported it over to WebExtensions.

There are three core reasons why an add-on may not be compatible with Firefox 57 anymore (when WebExtensions become exclusive): While popular add-ons like NoScript will likely be ported over thanks to Mozilla working with developers actively on implementing missing API features, the same cannot be said for other add-ons. What I mean by that is that WebExtensions capabilities won't match those of Firefox's current system. While that seems far far away right now, it is almost certain that things won't be ready by then.