Earlier quoted context omitted.
Why does it require a whitelist? If I make my own, do I have to contact Mozilla or is the user prompted when first access is attempted?
The protocol handler support is restricted to a whitelist to prevent an addon from taking over, say, " http://" (or other protocols which could be used to insinuate unsafe content).
Extensions in Firefox 59
211–220 of 243 posts
Re: Extensions in Firefox 59
#212Seems like we're getting closer with this version though. I might just have to be patient.
Re: Extensions in Firefox 59
#213Earlier quoted context omitted.
I'm waiting for them to include something like tree-style tabs by default in a future version :o
That'll never happen. Some casual users are confused by tab bars. And casual users understand trees even less.
Re: Extensions in Firefox 59
#214Earlier quoted context omitted.
That'll never happen. Some casual users are confused by tab bars. And casual users understand trees even less.
I’m confident that it will happen. It’s actually easier to understand tabs on the side for new users. And it makes more sense in general.
On the other hand, "never say never", right? :)
Re: Extensions in Firefox 59
#215I find this pretty exciting for (hopefully; someday) wider adoption of alternative protocols: Starting with Firefox 59, several protocols that support decentralized architectures are available for use by extensions. The white-listed protocols are: + Dat Project (dat://) + IPFS (dweb:// ipfs:// ipns://) + Secure Scuttlebutt (ssb://)
Hey! I made that patch! :-D so basically the explanation is simple. There is a whitelist of protocols you can have your WebExtension take over. If the protocol you want to control is not on that whitelist such as an hypothetical "catgifs:" protocol, you need to prefix it like: "web+catgifs" or "ext+catgifs" depending if it will be used from the Add-on or by redirection to another Web page. This makes it inconvenient…
However, I find the concept of the scheme whitelist pretty strange in context of WebExtensions.
Of course it makes sense that http:, https:, data:, blob:, etc should be off-limits for extensions. But on the other hand, I'd think that the primary use-case of registering protocol handlers in extensions is to handle existing links - something that the ext+/web+ rule seems to be particularly designed to disallow.
Apparently, the actual handler whitelist for WebExtensions can be found at [1]. It looks pretty... arbitrary?
For example, it's amazing to see that magnet: irc:, ssh: and gopher: are on there, but then why not ftp:, ws: or even steam:? There could be some useful extensions intercepting those as well.
Likewise, while the inclusion of scuttlebutt, ipfs etc is very good news, what makes them eligible now that didn't make them earlier?
Generally, I'd like to know by what process is that whitelist managed and what are the criteria to get on there.
(I understand it's derived from the official HTML5 whitelist [2]. To be honest, that one looks even more arbitrary - but of course has different security considerations, as it defines an API for the open web. The two lists also seem to have some differences, as e.g. gopher: isn't on the HTML5 whitelist while openpgp4fpr: is not on the extensions list.)
[1] https://developer.mozilla.org/en-US/Add-ons/WebExtensions/ma...
[2] https://html.spec.whatwg.org/multipage/system-state.html#cus...
Re: Extensions in Firefox 59
#216Earlier quoted context omitted.
Secure Scuttlebutt, check it out at http://scuttlebutt.nz
My question was actually: who's using Secure Scuttlebutt?
Re: Extensions in Firefox 59
#217Was hoping to see Web SQL make its way back into Firefox. Yes, it's been deprecated for years, but that hasn't stopped the browser makers with majority of market share (Google > Chrome, Apple > Safari) from continuing to ship it along with the strictly worse alternative (IndexedDb). Now that pretty much every language compiles to Javascript it's a shame to lose SQL functionality on the client. Shared model, shared va…
Re: Extensions in Firefox 59
#218Anyone working on this reading the thread? Can we ever expect an extension that will allow the far better tab management that Chrome has? Namely: Being able to scroll between tabs with the scroll wheel, and being able to select multiple tabs with shift/ctrl to drag them/merge them/close them/etc. It's crazy to me that Firefox's original selling point was tab management, and today Chrome's is so much better.
there is (was?) a firefox extension called Tab Wheel Scroll which is broken since WebExtensions The main reason I won't upgrade firefox. https://github.com/mthamil/Tab-Wheel-Scroll/issues/19 edit: there's hope!! https://bugzilla.mozilla.org/show_bug.cgi?id=1285812
Is that extension about changing the tabs with the wheel?
Re: Extensions in Firefox 59
#219Here's wondering how soon we'll see ActivityPub added, now that it's in the standards.[1] [1] https://www.w3.org/TR/activitypub/
Re: Extensions in Firefox 59
#220If you have an existing Chrome extension that relies on just the WebRequest API, how much effort is it to port to Firefox? Do things generally work without significant modifications? Are there lots of gotchas and small differences?