On Sunday, January 29, 2017 at 1:55:50 AM UTC+1, Sergey Rozhenko wrote: > So far I haven't been able to find any piece of rationale behind > https://bugzilla.mozilla.org/show_bug.cgi?id=1199718 getting WONTFIXed. And > that's weird, because there has to be an enormous reason to justify its > scrapping. > WebExtensions made perfect sense to me until this happened: > - Most extensions won't use it, would be easy to sign and won't break with FF > updates. > - Small percentage of extensions will make use of it to do the special things. > > Ability of addons to modify browser UI code is the defining feature of > FireFox. Considering that Mozilla evidently lags far behind Chrome in > manpower and resources, there's very little FF can do to compete if this > feature is lost. > It will lose most of "must-have" addons that power users of FF can't live > without and that make people use FF rather than Chrome, like those made by > Quicksaver: https://blog.mozilla.org/addons/2016/11/23/add-ons-in-2017/ > > So, again, this is a "life and death" kind of issue for FireFox and there > must be a "life and death" reason for scrapping native.js. What is it?
There are Chrome-like extensions in Firefox now, they are assumed to be sufficient for tweaking the browser's behavior: https://developer.mozilla.org/en-US/Add-ons/WebExtensions Then there's a new extension mechanism called native messaging which is available in two versions: - As a part of the Chrome-like extensions - Free-standing: https://addons.mozilla.org/en-US/firefox/addon/web2native-bridge-emulator/ _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
