5 ms·
> but at the cost of Firefox's more powerful extensions? What do you believe you'll be missing? Add-on authors say the new API will meet their needs. Giorgio M
by clouddrover 11y ago
> but at the cost of Firefox's more powerful extensions?
What do you believe you'll be missing? Add-on authors say the new API will meet their needs. Giorgio Maone, the author of NoScript, says he's satisfied with the direction of the development of the new API: https://hackademix.net/2016/03/09/webrequest-where-were-where-were-going/ https://hackademix.net/2016/03/09/webrequest-where-were-wher...
If you develop some add-on that needs features the new API doesn't currently provide then I'd say the best thing to do is to get involved with the development and get those features added.
- Veratyr 11y agoDoes the new API support things like tree style tabs [0]? This is one of the things I've failed to see other browsers implement. [0] https://addons.mozilla.org/en-US/firefox/addon/tree-style-tab/ https://addons.mozilla.org/en-US/firefox/addon/tree-style-ta...
- detaro 11y agoThe second link in the article goes to the WebExtensions overview page, which mentions "Tree Style Tabs" by name as something that new APIs need to be build for. https://wiki.mozilla.org/WebExtensions https://wiki.mozilla.org/WebExtensions
- clouddrover 11y agoIf it doesn't yet, it will. Support for add-ons like Tree Style Tabs has been on their radar since development of the new API started: 1. https://billmccloskey.wordpress.com/2015/08/21/firefox-add-on-changes/ https://billmccloskey.wordpress.com/2015/08/21/firefox-add-o... 2. https://wiki.mozilla.org/WebExtensions#Additional_APIs https://wiki.mozilla.org/WebExtensions#Additional_APIs 3. https://wiki.mozilla.org/WebExtensions/RoadMap https://wiki.mozilla.org/WebExtensions/RoadMap
- the8472 11y agoThat just means that certain popular addons will get the support necessary to have their needs satisfied. Some niche ideas won't get support and thus die. That's the problem with a gated system where you can only do things approved by HQ.
- JackC 11y agoI think this is the bug for implementing a sidebar API: https://bugzilla.mozilla.org/show_bug.cgi?id=1208596 https://bugzilla.mozilla.org/show_bug.cgi?id=1208596 It doesn't seem to be getting much traction so far -- maybe jump in and encourage? Chromium has wontfix-ed their sidebar API: https://bugs.chromium.org/p/chromium/issues/detail?id=344870#c113 https://bugs.chromium.org/p/chromium/issues/detail?id=344870... https://bugs.chromium.org/p/chromium/issues/detail?id=51084#c99 https://bugs.chromium.org/p/chromium/issues/detail?id=51084#... https://bugs.chromium.org/p/chromium/issues/detail?id=477424#c82 https://bugs.chromium.org/p/chromium/issues/detail?id=477424... I was sad to see that -- Tree Style Tabs is the killer Firefox feature for me. Maybe if Firefox can show the sidebar API works it'll get another hearing with Chrome as well.
- rndgermandude 11y agoQuite a few add-on authors say the direct opposite, that an WebExtensions only future will kill their add-ons and that there is no way mozilla will be able to provide enough APIs to stop that from happening. Some examples: - https://github.com/hultmann/multifox https://github.com/hultmann/multifox - http://www.chrisfinke.com/2015/08/21/my-future-of-developing-firefox-add-ons/ http://www.chrisfinke.com/2015/08/21/my-future-of-developing... - http://www.downthemall.net/the-likely-end-of-downthemall/ http://www.downthemall.net/the-likely-end-of-downthemall/ PS: It goes without saying that Giorgio and NoScript due to their popularity and because Giorgio is very well networked within mozilla get a lot of special treatment an add-on that has only a couple of hundred or thousand users will not. This isn't a bad thing, for NoScript at least, but does not help other add-on developers.
- clouddrover 11y ago> This isn't a bad thing, for NoScript at least, but does not help other add-on developers. You should read Giorgio's blog post. The API features NoScript needs also help FlashGot, Ghostery, RequestPolicy Continued, ad blockers, and similar add-ons. Both multifox and Chris Finke's blog posts are not saying their add-ons aren't possible with the new API, just that they don't want to rewrite them for the new API. Chris Finke is looking for new maintainers for his add-ons. Why don't you become the new maintainer for, say, RSS Ticker (or another of his add-ons) and port it to the new API? See RSS Ticker's page: http://www.chrisfinke.com/addons/rss-ticker/ http://www.chrisfinke.com/addons/rss-ticker/
- rndgermandude 11y agoYes, try to spin it all you like, it does not change the facts, which are: * NoScript is getting preferential treatment. That this also has positive outcomes for a handful other (block something) add-ons does not change this or address the situation at large. Add-ons on Firefox are so much more than just fiddling with some web requests. * Not all add-on authors are happy with WebExtensions or think they will be able to "port" their add-ons, if not for lack of APIs then for time constraints. * Thousands of add-ons will be broken. While many can be "ported" as you put it (which is usually an entire rewrite), it is far from clear how many will be actually rewritten by the original developers or somebody else, and how many will be just abandoned or cannot be ported at all.
- kuschku 11y agoEffectively, what we need, is the ability to modify 100% of the browser chrome as if it was just another website. If they want to drop XUL, they should first finish browser.html
- DarkLinkXXXX 11y agoWhat about DownThemAll? Is this just uninformed FUD? http://www.downthemall.net/the-likely-end-of-downthemall/ http://www.downthemall.net/the-likely-end-of-downthemall/
- RubyPinch 11y agoprobably just unintentional fud what is needed for a DTA-like, is some way to make arbitrary connections with arbitrary headers (which I would be surprised if it isn't provided), some way to write to a file with some reasonable control over how that file is written (writing and seeking, not the most needed thing, but would obviously be preferred), and some way to display UI (a html panel) This might be harder or easier to implement than DTA is, but there probably won't be a direct port of DTA ever due to how tightly coupled it is with firefox
- clouddrover 11y agoI'd say it's FUD from 8 months ago. In that blog post they say that NoScript and Tree Style Tabs will no longer be possible with the new API. Meanwhile the author of NoScript says the new API works for him and Mozilla is making sure the new API provides the features that add-ons like Tree Style Tabs need. No need for fear, uncertainty, or doubt.
- drdaeman 11y agoThe old XUL (non-restartless/jetpack) extensions are currently about the only way I know to actually hack on the browser's core without having to patch omni.ja and having to set disable_xul_cache, which is quite a terrible way to extend the browser. If even those are removed or blocked, there won't ever be a way (ok, a way without explicit Mozilla's blessing) to implement custom password stores (think OS X Keychain, KDE KWallet or GNOME Keyring), or a custom sync engine, or tree-style tabs. And with WebExtensions I can't find (maybe that's me, though!) an equivalent of preferences/service Add-on SDK API.
- yoklov 11y agoRegarding needing to implement a custom sync engine, what would you want that isn't provided by https://wiki.mozilla.org/WebExtensions/chrome.storage.sync https://wiki.mozilla.org/WebExtensions/chrome.storage.sync? Genuinely curious.
- drdaeman 11y agoI had always assumed chrome.storage.sync API is all about using sync rather than implementing it. I.e. extension acts as a client, rather than provider. I mean, that API already provides a localStorage-like objects that one can use to put and get data. Technically, one can listen for events and have a custom backend this way, from my understanding, this is extension-local, and not browser-wide interception. Now I wonder - maybe I got it all wrong? Does it actually allow to completely override built-in Firefox Sync (and either ditch Firefox Accounts requirement for Sync engine to start[1], or override those as well) and replace those parts with a custom implementation? Say, I don't want any Mozilla nonsense, and want Firefox to sync with a simple WebDAV storage (rather than their proprietary protocol), and do so authenticated with a sane(r) X.509 client cert rather than an ugly mess of BrowserID, HAWK and OAuth2. Is that possible? ____ [1] This part is probably easy through messing with browser's preferences (the ones in about:config), but I'm not sure there's a WebExtensions API for this. Have looked for it and haven't found anything.
- the8472 11y ago> What do you believe you'll be missing? Old extensions have access to js-ctypes. Which means it can do anything libc/any native library does. Spawning processes, filesystem access, interacting talking to native applications (no, connectNative definitely does not count, because it requires opt-in and special support and thus does not provide interoperability) They can also freely manipulate the browser UI. Chrome extensions can't do either of those. Mozilla has some future plans on providing extensibility, but as long as those are just plans without any schedule or implementation i'll remain pessimistic that it'll still result in a reduction of available feature space.