What to me also is not a sign of good PR is that the WebExtension logic is not even designed in a way that add-ons which are created as a response of removing logic from Firefox (as is the case with gopher support in case on Cameron’s add-on). (Which should be relatively easy to check based on the stats from amo). I would also help if the WebExtension-logic would be feature complete with at least the top 25 add-ons used at the moment. (which I already said when commenting on the add-ons blog when it comes to this switch).
I would personally appreciate it if you could discuss at least the part related to changing the switch moment to be just after another Long Term Support Firefox has been releases. Somehow all comments I (and possibly others) made related to feature completeness of WebExtensions vs XPCOM/XUL seem to be have fallen on deaf ears when it comes to the people responsible for the add-on/extension Hopefully your experience will be a wake-up call for the developers & managers responsible for this. Today I noticed a complaint about missing features in WebExtensions on Cameron Kaiser’s blog ( ). When 70% of the add-ons of the average user no longer work after upgrading to Fx 57 somewhere in the planning of the deprecation something went wrong.Īlso the comment made by Wladimir Palant related to the stability of WebExtensions are also not very encouraging. To me this experience you have indicates that the Mozilla developers clearly are not as close in touch with the extension developers as should be needed.
In my opinion they should at least ensure that the switch is done in tandem with a release of a Long Term Support Firefox (which then gives users a possibility to keep using their classic extensions for about a year after the classic XUL/XPCOM have been forced out the normal Firefox codebase). Īlthough you may not be a typical user your experience with this switch to WebExtensions should be a warning for the people forcing this switch. This entry was posted in Mozilla, Syndicate by gerv. I fully admit I may not be a typical user, but it seems like this will not be my experience… :-( In the Firefox (I think it was) Town Hall, there was a question asked about addons and whether we felt that we were in a good place in terms of people not having a bad experience with their addons stopping working. As for the rest – who knows? There doesn’t seem to be a way of finding out other than researching each one individually.
#Best firefox youtube downloader addon plus
I’m sure Adblock Plus is being updated, because it would be sheer madness if we went ahead and it was not being. Useful addons which will also no longer work in 57 (if nothing changes) include: Adblock Plus, HTTPS Everywhere, JSONView, and Send to Kodi.
#Best firefox youtube downloader addon password
Useful addons which no longer work as of now are: 1-Click YouTube Video Downloader, Advertising Cookie Opt-Out, AutoAuth, Expiry Canary (OK, I wrote that one, that’s my fault), Google Translator, Live HTTP Headers, Mass Password Reset, RESTClient, and User Agent Switcher.
Firefox Nightly (will be 56) already no longer supports addons which are not multiprocess-compatible.
0 kommentar(er)
