3 ms·
It's been tried[0][1][2], but doesn't work very well. Similar to how PhoneGap tries to create a cross platform solution, it will always feel kludgy compared to
by nathancahill 11y ago
It's been tried[0][1][2], but doesn't work very well. Similar to how PhoneGap tries to create a cross platform solution, it will always feel kludgy compared to developing with native APIs.
[0] http://kangoextensions.com/ http://kangoextensions.com/
[1] http://crossrider.com/developers http://crossrider.com/developers
[2] http://crossbrowser.com/ http://crossbrowser.com/
- kuschku 11y agoWell, with this new API Chrome extensions run natively in Firefox, if one adds a single tag to the metadata json file. So, doing this should be easy.
- nathancahill 11y agoI wouldn't phrase it like that. Instead, Firefox is implementing a similar extension API, which overlaps with Chrome and Opera's APIs. What you described, "instantly converting an existing Chrome extension for Firefox" is a long ways off. There's a lot of gaps in Mozilla's implementation right now. To do anything interesting (beyond cat gifs), you have to fall back to the old QueryInterface/ns* APIs.
- voltagex_ 11y agoAre we still allowed to use the old APIs? See http://www.downthemall.net/the-likely-end-of-downthemall/ http://www.downthemall.net/the-likely-end-of-downthemall/
- nathancahill 11y agoFrom the original post[0]: > A major challenge we face is that many Firefox add-ons cannot possibly be built using either WebExtensions or the SDK as they currently exist. Over the coming year, we will seek feedback from the development community, and will continue to develop and extend the WebExtension API to support as much of the functionality needed by the most popular Firefox extensions as possible. [0] https://blog.mozilla.org/addons/2015/08/21/the-future-of-developing-firefox-add-ons/ https://blog.mozilla.org/addons/2015/08/21/the-future-of-dev...