Skip to content
This repository has been archived by the owner on Dec 11, 2019. It is now read-only.

Implement about:config #545

Closed
ghost opened this issue Feb 1, 2016 · 13 comments
Closed

Implement about:config #545

ghost opened this issue Feb 1, 2016 · 13 comments

Comments

@ghost
Copy link

ghost commented Feb 1, 2016

We need a way of configuring the browser at some point. I understand this is expermiment at this point but we need a way to control proxy usage, hybernate technologies that users don't want to run as well as homepage settings.

I know this browser takes privacy seriously but their is a danger in billing this is a privacy browser if we don't yet have the features implemented to allow users control over their footprint.

@bbondy
Copy link
Member

bbondy commented Feb 1, 2016

++ I'm working on some about pages this week, about:newtab placeholder and about:preferences. After that's done it'd be a good time to add a more dev-friendly about:config to expose advanced things.

@luixxiul luixxiul changed the title Implement about:config or provide way to control RTC and DNS leaks Implement about:config May 15, 2016
@bbondy bbondy removed their assignment May 15, 2016
@halo
Copy link

halo commented Jun 17, 2016

I would just like to mention that configuring the browser via command-line would be helpful for mass-deployment. Having multiple machines makes me not want to spend much time clicking around manually in about:config 10 times (though it's certainly useful if you only have one installation of Brave).

It's tedious to configure browsers in an automated way (except maybe Safari). Brave could stick out here as a little more developer-friendly. Someone suggested even a .braverc file that holds advanced configurations. Now, that would be innovative! :)

Looking to and fro the issues, I found the defaultSettings but I'm puzzled as to where exactly these are persisted on my drive (in fact, I'm not even sure whether electron is responsible for handling this or not).

@exec
Copy link

exec commented Jan 25, 2017

Definitely support this concept, would be great to have more advanced config options.

@LaurenWags
Copy link
Member

+1 from community: https://community.brave.com/t/similar-about-config/5088

Specifically user would like to see these items on this page: WebRTC; webgl; Prefetch; disableIPv6; Referer Header; enable or disable 3DES cipher; HTML5 ping

@stevespringett
Copy link

For me, I need to disable webassembly for various security reasons. I have it disabled in Firefox and Chrome, but unable to disable it in Brave.

@cezaraugusto cezaraugusto added this to the Triage Backlog milestone Nov 8, 2017
@eljuno
Copy link
Contributor

eljuno commented Jan 15, 2018

@eljuno
Copy link
Contributor

eljuno commented Mar 24, 2018

@EvilGnome6
Copy link

+1.

I would like the ability to change the following settings:

  1. Don't load pinned tabs until I select them.
  2. Don't replicate pinned tabs to new Windows.

@krmbzds
Copy link

krmbzds commented Jun 4, 2018

+1

I agree with everything mentioned above.

In addition, I would like to disable conflicting shortcuts.

These shortcuts conflict with Spectacle:

  • ⌥ + ⌘ + →
  • ⌥ + ⌘ + ←

Behavior:

  • Resizing the window to the right half of the screen also switches to the next tab.
  • Resizing the window to the left half of the screen also switches to the previous tab.

Same thing should apply for other conflicting shortcuts as well.

@ci70
Copy link

ci70 commented Sep 13, 2018

Why has this not been implemented yet???
Whats the point of this browser if I can configure it.. this has to be a joke right?

@stevespringett
Copy link

@joeparkerz actually, it has been implemented. The Brave Dev version incorporates this. So you can now go to chrome://settings/ or chrome://flags/ for example. And of course you can go to chrome://about/ to list all the internal URLs. The Dev version is very much like Chrome though, same look, same config, etc. They no longer seem to be hiding the fact that its built on Chrome.

I haven't personally tested it, but it is there.

@ci70
Copy link

ci70 commented Sep 13, 2018

You can't be serious. chrome:flags, chrome:settings are both available on Chrome!
So what kind of advantage am I getting here?

@bsclifton
Copy link
Member

@joeparkerz you can open an issue in our new repo, https://github.com/brave/brave-browser/issues, and describe the functionality you'd like to see

As @stevespringett said, with this new code-base, all of the chrome pages are available. That combined with no comments in a while is why I had closed this issue. This is a feature we will not be adding to the Muon version of our product (ex: browser-laptop)

@bsclifton bsclifton added wontfix and removed stale labels Sep 13, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests