Easier Enabling of Extensions

[Krutonium]

I ask because I have several addons that I would need to be able to truly move to this browser - LastPass for example for many people, would be a dealbreaker.

[diracdeltas]

Compatibility with Chrome extensions is a good post-1.0 goal. The main reason it's not coming earlier is that Electron doesn't want to support all the Chrome extension APIs; we'd have to convince them to do so or put them in our fork of Electron. electron/electron#1498

[wrkerr]

This is a really important enhancement for me. I daily move between an Android phone, a linux home desktop, and a Windows work laptop. There are a handful of extensions that provide some important security and integration funcationality.

Like the OP, I too need integration from a cross platform password manager, though preferably not one that stores your password database on their servers like LastPass. Enpass and Keepass are primary examples, though there are others. These are particularly effective when combined with an extension like Authy, which makes two-factor authentication much simpler.

Additionally, I would love to have support for some browser integration with a secure messenger that interfaces with android messaging. Signal Private Messenger by Open Whisper Systems is developing a Chrome web app desktop interface that would be wonderful to have. Telegram and others provide similar feature sets.

Lastly, there are several services which leverage browser extensions to provide a simple way to share text, links, and files between devices. Join and Pushbullet are two popular examples, and their browser extensions provide a great deal of multi-device integration and convenience. This would be a great addition.

All of these could be achieved if Brave gained support for Chrome extensions and web apps, rather than creating another ecosystem of exensions.

[weems]

@wrkerr definitely in plans, but we have to prioritize what will be in 1.0 so as to move as fast as possible and meet schedule on time :) Might want to check https://brave.com/dev_timeline.html

[wrkerr]

@weems, that makes sense to me. Thanks!

[diracdeltas]

Talked to @bridiver about this just now. We will probably implement all/most of https://wiki.mozilla.org/WebExtensions, which will cover the majority of functionality needed for chrome extensions.

[Krutonium]

Wait, so Brave will support both Firefox AND Chrome extensions?

[bridiver]

@PFCKrutonium No, the webextensions are Mozilla's effort to support Chrome extensions, but we will not support FF only extensions

[Krutonium]

Ah okay.

[samhh]

Glad to see this is planned! +1

[ghost]

I'm also looking to develop an online service that needs a plug-in and I would really like 100% coverage. Chrome compatibility is a small plus because that's one less browser to support but it's more important to me at least that there is some way to target the browser.

I worry about Electron being able to support chrome extentions in a way that won't be buggy. I feel bad for them being asked to support that and seeing as that's not even on their time table, much less on their time table but unrealistic, I'm a +1 for a rudementry add-on system. Atom, which electron is coded for seemed to have no problem doing it at that layer. That's another reason why Electron won't include chrom plugins. It's not on Atom's radar so it won't be on Electon's. Could you imagine how borked Atom could get if people injected extensions in there?

They forked Electron from Atom so people to could work on it to make it more stable for Atom. They aren't going to accept features that could create pains for Atom even if by mistake.

[bridiver]

well, it's not really practical for Electron to have 100% coverage because a lot of API functionality depends on the specific app you have implemented. For instance: browser action popup windows can be triggered with generic functionality in Electron, but it's impossible to know how an app will actually want to display them. They are interested in pulling in some extension functionality and there is an open ticket for it, but I'm not sure how much of it we will be able to upstream. I'm doing my best to make the implementations as generic as possible, but there's no guarantee everything will make it to upstream. I'm also using the chromium code where possible (background pages, chrome.runtime and a few others).

[bridiver]

also, it's entirely up to the app whether or not they want to expose the ability to install extensions. I even left in checks that allow you to build electron with extensions disabled. So far we have not exposed the ability to install user extensions because the extension support is limited and we haven't implemented all the permission checks necessary to ensure the safety of unknown extensions

[nickschurch]

I'll add my voice to the need for some browser apps - keepass/lastpass is a must for me.

[thekevinbrown]

As a developer on Toolkit for YNAB I'd love to be able to support Brave as a platform.

[luixxiul]

FYI: LastPass has been integrated already.

[bridiver]

@nickschurch I was not able to find an "official" keepass extension for Chrome. There appear several extensions that support it to some degree, but I think it will likely have to wait until we have full extension support

[dogancelik]

You can use KeePass in Chrome and Firefox by using:

• Chrome extension: Hostname in Title
• Firefox extension: KeePass Helper

Then enable "An entry matches if the host component of its URL is contained in the target window title", hope this helps.

Also Chrome extensions are not really necessary right now but allowing users to customize their pages with Userscripts would be a good addition.

Userscript is a script that works on Opera, Safari, Chrome (6.6m users) and Firefox (1.2m users)

[ElijahLynn]

https://github.com/brave/browser-laptop/wiki/Brave-Development-Timeline

Says, 1Password, Dashlane and Lastpass are implemented.

[bridiver]

we have partial extension support right now and we're working towards full support. We won't have full support in 1.0, but we are hoping to add more extensions based on popularity. Without full chrome.* api support we really need to test each one right now

[ElijahLynn]

I am on .10 (Linux), I see support for 1Password and Dashlane in Preferences > Security. I am assuming .11 has the initial support for Lastpass?

[bridiver]

actually that's a bug, 1Password should be disabled on Linux because they don't have a linux client app. Lastpass should work, but it's currently missing a few options and is only accessible through the right-click context menu. You will need to update to 0.11 for Lastpass

[ElijahLynn]

Awesome, just updated and Lastpass is working flawlessly! I am now posting this from Brave! Sooo fast!!! MMMMMm..

[stri8ed]

I am very much interesting in using Brave to try out the Bitcoin integration, but until there is support for WebExtensions, I cannot make the switch from Chrome.

Adding extension support on a per-extension basis is not a great solution imo. Since you will never satisfy all users needs. All it takes is one missing extension for a user to abandon Brave in favor of an alternative.

[Kinnardian]

Is there a listing of extensions/add-ons that work already?

[qazip]

How is the support for chrome extensions going? I suppose one can not use chrome extensions on brave yet?

I'm looking for support to the following:

• ublock origin (I know you've support for blocking ads, but, for some reason, the invisible space is not being collapsed. I would also like to remove twitter, FB (etc) widgets. I can't seem to do that easily in Brave);
• Vimperator: I need vim-like behaviour;
• Dark background with white text: It blinds me having to read pages with white background;
• Pinboard extension;
• User agent spoofing could be helpful as well (not sure if Brave supports that, but on panopticlick.eff.org, I'm always unique in Brave, even with Fingerprint protection enabled);

[ElijahLynn]

+1 for Vim-like extension (or native support), scrolling, back/forward etc.

[c-u-b]

any advice on how to get kinjamprove on brave?

[jonathansampson]

@c-u-b Would you mind testing the extension? https://medium.com/@jonathansampson/testing-chrome-extensions-in-brave-8e25d1f7386d

[c-u-b]

@jonathansampson i have briefly glanced at the instrux on medium, and it appears i need to install chrome. is there any other way?

[bsclifton]

@jonathansampson aren't there command line tools available via NPM that you can package / unpack chrome extensions?

[tbartlett0]

I would like to add my voice to the request for this. Perhaps if it was done similar to the way Firefox can temporarily load an extension through the "about:debug" page... this would make it a lot easier (and therefore more likely) that I would test extension that I'm interested in.

[nickytonline]

@bsclifton, it's chrome-ext-downloader, npm install -g chrome-ext-downloader. See https://brave.com/loading-chrome-extensions-in-brave for info on how to do the whole song and dance. ;)

[bsclifton]

@nickschurch thanks- I meant to give an update but totally forgot

For everyone subscribed here: I created an experimental extension branch back in December which folks can try here (if you're up for running from source):
https://github.com/bsclifton/browser-laptop/tree/experimental-extensions

Here's the commit which does the magic (which includes testing steps):
https://github.com/bsclifton/browser-laptop/commit/b777047fabc08c4e077226541ca4caa7e1cd633f

I tested this out by downloading/installing about 20 extensions and they all seemed to work good (I'll admit, I didn't test in depth). For folks wanting to try extensions, I'd highly recommend pulling down my fork (or just apply that patch on master)

[tbartlett0]

@bsclifton I've had a go at building from your fork but no success yet - haven't had time to troubleshoot what went wrong. Also, that's in a dev VM so I won't be able to run extensions on my main Windows install unless I can get a build running on there too... I'm a bit scared to try!

I hope there is an option to enable this as a 'debug feature' in one of the official builds sooner or later...

[illegalnumbers]

So what troubleshooting and dev tasks are still required to get things enabled?

[bsclifton]

I'm going to close this as wontfix... because it will be addressed with Brave Core - the upcoming version of Brave which uses a forked Chromium UI instead of Muon. We already have this installing extensions just fine and the build in chrome://extensions/ page works great (you can load unpacked extensions, etc)

We should have a build of this new Brave available in a few months- hang tight 😄

[rdbox]

add this application Privacy Possum allows you to block and randomize the fingerprint

[Zerophase]

Doesn't the new version for release in October support all Chrome plugins?

[cndouglas]

@Zerophase Yes. A developer release of the new version is already available: https://brave.com/download-dev

[pkieltyka]

can we get an update on current status of a public/stable release for this? I need it before I can move over to Brave

[bsclifton]

@pkieltyka we launched brave-core on our Beta channel recently, which you can find here:
https://brave.com/download-beta

Per our release schedule, we're targeting a stable release of brave-core just over a week from now (2018 Oct 16)

After the release channel ships, we'll (schedule undecided - but likely in the next few months) work on having this version of the browser update itself to brave-core