4 ms·
Now someone just needs to write a small converter that instantly converts an existing Chrome extension for Firefox, and a script that allows people to install f
by kuschku 11y ago
Now someone just needs to write a small converter that instantly converts an existing Chrome extension for Firefox, and a script that allows people to install from the Chrome market, too, and instantly the available extensions for both browsers doubles.
- wldcordeiro 11y agoMost Firefox extensions are still in the older formats but it'd at least get a cross-browser extension system working.
- kuschku 11y agoWell, Firefox users would still have an advantage. That Chrome users will never get addons that add tree-style tabs, or completely modify the UI, etc, is obvious. But from that point on Chrome does not have many things above Firefox anymore.
- geofft 11y agoFor users who primarily care about extensions, but that's been true for a while. I rarely use extensions (currently I'm using, uh, Google Cast, plus the mosh Chrome app because life's too short to install software) and I care about security, and Chrome's multiprocess and sandboxed architecture has significant wins there. When Firefox gets that, then I'd agree that at least for me, Chrome won't have many things above Firefox any more. And the new extension system is part of their plan for getting there.
- chimeracoder 11y ago> Chrome's multiprocess and sandboxed architecture has significant wins there. When Firefox gets that, Multiprocess is currently enabled by default on desktop in the Firefox developer edition. And the release version of Firefox on Android is multiprocess and also supports extensions.
- Tobu 11y agoIn practice, about half the extensions I use (the complex ones, like Lazarus) need a serious overhaul to work with e10s. It can't hit a stable release, there would be major breakage.
- viraptor 11y agoThere's a difference between chrome and ff multiprocess. The sandbox model (at least on linux) in chrome is better than anything else available right now. They're pretty much the reason that kernel-level sandbox is available to us now.
- geofft 11y agoHm, both viraptor and I were downvoted without significant commentary. While I don't mind downvotes for being wrong, is anyone interested in actually claiming that we're wrong? As far as I'm aware, viraptor is completely technically accurate: the Chrome team is the reason that Linux's seccomp mode 2 is so good today. (In 2010-11 I was working on a project that assumed that the seccomp mode 2 rumors were never going to amount to anything, which was the consensus of the time.) Also while I'm here, a certain [dead]-and-proud account linked this bug which is somewhat relevant (but only somewhat, in my eyes): https://code.google.com/p/chromium/issues/detail?id=477424 https://code.google.com/p/chromium/issues/detail?id=477424
- kuschku 11y agoI don’t know enough about the sandbox model to discuss it (and I know that Google tries to have an amazing sandbox model especially because they run their browser also as OS) But the sidebar stuff just can’t compete with the whole browser UI being effectively an XML document in the hands of an extension.
- viraptor 11y agoThere were lots of interesting extensions doing crazy stuff with the UI at the beginning. Then they got split into some specific types, like: icon/action, content processing, extra information (typically as a side/top/bottom bar). To the point that I can't even think of one that doesn't fit in those scenarios. The extension authors were invited to comment on what's needed from the extension API to support their use case. So are you one of the extension authors, or users? What exactly do you want to change in the UI and did you raise an issue with google or mozilla?
- ossreality 11y agoYeah, except reality: https://code.google.com/p/chromium/issues/detail?id=477424 https://code.google.com/p/chromium/issues/detail?id=477424
- nathancahill 11y agoIt'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...