Is this statement below true? If so I will be forced to use another browser. These are safe and well functioning extensions I have installed from trusted web developers. … (閱讀更多)
Is this statement below true? If so I will be forced to use another browser. These are safe and well functioning extensions I have installed from trusted web developers. I have trusted Firefox since, well "forever", and now limiting or even causing my extensions to stop functioning is bad. So upset about this and after all these years of having a functioning browser with the ease of making it more my own and having limited use such as with Chrome, Safari or IE is far the worst decision I have ever seen in the history of Mozilla.
Hoping some feedback from others may help the developers make a better decision, and hoping Firefox can remain in the top for user-friendly experience.
There are enough FREE web extensions out there to protect us all from malicious web sites and virus protection programs we all can use to keep us safe on our computers and web, why would a decision be made to limited extension security be implemented when all is working fine. Even my McAfee SiteAdvisor and Avast Online Security are showing they cannot be verified now with version 40. Ridiculous and bad for consumers who have always liked and trusted Firefox for a more user-friendly experience.
August 21, 2015
Mozilla just announced their intent to deprecate so called XUL-based add-ons in favor of what they call the WebExtensions API within the next year or two. The WebExtensions API is supposed to be mostly compatible to Chrome/Safari extension APIs.
What does this mean for XUL-based add-ons? Well, for starters, Extensions will be dead if XUL-based add-ons with XPCOM access are gone. Simple as that. The new APIs would only allow for a severely limited in functionality, severely stripped down Extensions at best.
Gone will be add-ons that e.g. let you change major bits about the Firefox user interface (e.g. tabs tree add-ons), add-ons that allow you to do more “advanced” stuff than just showing or slightly altering websites, such as e.g. restarting the browser upon click (unless mozilla kindly provides an API for that, which won’t be compatible with Chrome, of course). Add-ons like NoScript will be severely limited in their feature set as well. Say byebye to Greasemonkey and hello to Tampermonkey, with it’s limitations. Want that add-on that lets you change the new tab page for something else or enhances that page? Maybe it will be available, maybe not, depending on if and when mozilla kindly provides WebExtensions APIs for such things. And of course, depending on if there will be an author creating this entirely new add-on from scratch.
What this also means: Almost all your existing add-ons will be broken, entirely, save for some Add-on SDK add-ons, namely those that don’t do anything fancy. Sure, even today, lots of add-ons break, and some add-ons will not get updated when they do and there are no suitable replacements. However, with this change, almost every add-on will be completely broken and in need of major updating by the extension authors. Good luck with that.
It is safe to say, that Firefox will not be Firefox anymore as far as extensions go, but instead will become yet another Chrome-clone.
To be clear: I was furious when the extension signing stuff was announced and then actually implemented, which effectively created yet another Walled Garden, but regarding this announcement I am just sad. Right now, it feels like I just learned my dear old friend Firefox is going to die.