Batu69 Posted May 13, 2017 Share Posted May 13, 2017 Mozilla plans to add a feature to Firefox 57 which enables users to find replacements for extensions that are no longer supported by the browser. The release of Firefox 57 will make major changes to the browser's add-on system. Legacy add-ons, those that are not WebExtensions, won't be supported anymore as Mozilla plans to focus solely on WebExtensions, a technology used by browsers such as Google Chrome as well. One effect of the change is that part of Firefox's user base will end up with incompatible add-ons. That's a usability issue obviously as users will end up without functionality provided by these add-ons. Note: Mozilla marks those add-ons as legacy in Firefox Nightly already. This will come to Firefox Stable as well in time as an indicator that these add-ons will stop working in Firefox 57. Up until now it was not really clear if and how Mozilla wanted to address the issue. It appears, that the organization has found a way. Find a replacement Mozilla plans to add a new unsupported listing to the add-ons manager. You can load the add-ons manager by entering about:addons directly, or with a click on the main Firefox menu button. All extensions that are no longer compatible when the change hits the browser are moved to that section. This means, that they are not removed right away from Firefox either, but kept for the time being. 40% of Firefox users don't use add-ons according to a 2016 Mozilla study. Those won't notice the change at all. Tip: Check out Top Firefox add-ons and their WebExtensions status for an overview of what is compatible already, and what is not. Also, find out which Chrome extensions will run in Firefox, This is good for two reasons: first, because users may notice that the extensions are unsupported. This would not be the case if Mozilla would just delete the add-ons, as users would be left puzzling what happened to them. Second, because it allows Mozilla to add the recommendation feature to the unsupported extensions listing. The main idea of the feature is to suggest supported extensions -- read WebExtensions -- as alternatives to unsupported legacy add-ons. All that users need to do is click on the "find a replacement" link, to get suggestions for comparable add-ons. The feature is not live yet, but a click on the link will redirect the request to the Mozilla Add-ons website where replacements are then listed on a page. A couple of things may happen when users click on the button: A WebExtensions alternative that replicates all, or most of the add-ons functionality is suggested. Suggestions match some functionality only. No alternatives are available because a) no one created one, or b) the APIs don't support it anymore. You probably wonder how many extensions will remain compatible with Firefox. You can find that out here. Closing Words The cut that Mozilla makes in Firefox 57 impacts part of Firefox's user base. While there is no study about that, at least none that got published, I'd estimate that it will hurt veteran Firefox users more than it will hurt new users of the browser. It is clear already that functionality that some legacy add-ons or themes provided won't be supported by WebExtensions, and that these add-ons or themes won't be available anymore, nor will any alternatives to those because of this. The find a replacement feature will certainly help some users provided that it works correctly, and that is a good thing. (via Sören) Article source Link to comment Share on other sites More sharing options...
Karlston Posted May 15, 2017 Share Posted May 15, 2017 I'll be trying Firefox 57 in a VM. But if I can't get the UI and functionality the way I want it, then I'll stay on 56 or move to 52 ESR. I know that Classic Theme Restorer will not/cannot be ported to Web Extensions and others extensions like GreaseMonkey are not certain to make it. The Firefox updater will (of course) update Firefox to 57 and THEN tell you all the installed extensions which are now broken. Why do it in this user-unfriendly order? Because keeping software/OS up to date immediately is infinitely more important than usability and will also stop the universe and space-time continuum from imploding, just ask Microsoft... Tap, tap, tap... that's the sound of Mozilla hammering yet another nail into Firefox's coffin. Link to comment Share on other sites More sharing options...
Batu69 Posted May 15, 2017 Author Share Posted May 15, 2017 20 minutes ago, Karlston said: The Firefox updater will (of course) update Firefox to 57 and THEN tell you all the installed extensions which are now broken. Why do it in this user-unfriendly order? Because keeping software/OS up to date immediately is infinitely more important than usability and will also stop the universe and space-time continuum from imploding, just ask Microsoft... About your case, Mozilla not add this feature yet for unsupported extensions, Mozilla just plans. I think this feature will come on stable release. Quote Mozilla plans to add a feature to Firefox 57 which enables users to find replacements for extensions that are no longer supported by the browser. Quote Note: Mozilla marks those add-ons as legacy in Firefox Nightly already. This will come to Firefox Stable as well in time as an indicator that these add-ons will stop working in Firefox 57. Quote The move blocks any non-WebExtension add-ons from working in the browser. In fact, users won't be able to install legacy add-ons when Firefox 57 hits, and the add-ons that they had installed before the upgrade to the new version of the browser won't be there anymore after the upgrade. It is a clear cut that Mozilla plans, one that is welcome by some and disliked by others. For Mozilla, moving Firefox's extensions system to WebExtension exclusively means a reduction in extension caused crashes and performance issues, the freeing up of development time because extension compatibility is less of an issue, and that users won't face that many issues anymore caused by add-ons. Firefox Nightly marks Legacy Add-ons Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.