Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Move WebTorrent setting switch to brave://extensions #2851

Open
srirambv opened this issue Jan 8, 2019 · 3 comments
Open

Move WebTorrent setting switch to brave://extensions #2851

srirambv opened this issue Jan 8, 2019 · 3 comments

Comments

@srirambv
Copy link
Collaborator

@srirambv srirambv commented Jan 8, 2019

Description

Current implementation of WebTorrent switch is in brave://settings. It would be convenient to move it into extension page so that users find it easy to enable/disable as an extension as opposed to a setting

@srirambv srirambv added this to the 1.x Backlog milestone Jan 8, 2019
@rebron rebron added this to Untriaged Backlog in General Jan 8, 2019
@rebron rebron moved this from Untriaged Backlog to P3, P4, & P5 Backlog in General Jan 8, 2019
@tomlowenthal
Copy link
Member

@tomlowenthal tomlowenthal commented Jan 11, 2019

It's an integrated feature, so I don't know why someone would look for it under the extensions manager.

General automation moved this from P3, P4, & P5 Backlog to Completed Jan 11, 2019
@tomlowenthal tomlowenthal modified the milestones: 1.x Backlog, Dupe / Invalid / Not actionable Jan 11, 2019
@tomlowenthal tomlowenthal removed this from Completed in General Jan 11, 2019
@2635599
Copy link

@2635599 2635599 commented Jan 11, 2019

"Move WebTorrent setting switch to brave://extensions"

1,000% on board with this, and when we get switches for rewards and shields having them in extensions as well. tomlowenthali think most peeps are going to look their in settings. if it's left in settings then i think it needs to be in a group with rewards and shields by themselves.

@bbondy
Copy link
Member

@bbondy bbondy commented Jan 14, 2019

I think we could have it in both places, but no urgency to do that. So will re-open.

@bbondy bbondy reopened this Jan 14, 2019
@bbondy bbondy modified the milestones: Dupe / Invalid / Not actionable, 1.x Backlog Jan 14, 2019
@tomlowenthal tomlowenthal removed the wontfix label Jan 14, 2019
@rebron rebron added this to P3, P4, & P5 Backlog in General Jan 15, 2019
@rebron rebron moved this from P3 & P4 Backlog to P5 Backlog in General Jan 15, 2019
@rebron rebron added this to Untriaged backlog in Settings Jan 23, 2019
@rebron rebron moved this from Untriaged backlog to P5 backlog in Settings Jan 28, 2019
@rebron rebron removed this from the 1.x Backlog milestone Feb 7, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
General
  
P5 Backlog
Settings
P5 backlog
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
5 participants
You can’t perform that action at this time.