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.

Sign up for GitHub

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

Jump to bottom

Make Tor support per tab #33

Closed
bbondy opened this issue Dec 5, 2017 · 2 comments
Closed

Make Tor support per tab #33

bbondy opened this issue Dec 5, 2017 · 2 comments
Labels
browser-laptop-parity closed/invalid closed/wontfix feature/tor priority/P5 Not scheduled. Don't anticipate work on this any time soon.

Comments

@bbondy
Copy link
Member

bbondy commented Dec 5, 2017

Building on #32 but with Tor support
@bbondy bbondy added this to the Milestone 4: Post 1.0 releases milestone Dec 5, 2017
@riastradh-brave
Copy link
Contributor

Misread, this is specifically about per-tab Tor support, not about Tor support in general (#177).

cezaraugusto pushed a commit that referenced this issue May 15, 2018
@bbondy
Merge pull request #33 from brave/override_cc
6d02af7 
override cc files during compilation
@bbondy bbondy changed the title Tor private tabs Make Tor support per tab Jun 6, 2018
@bbondy bbondy modified the milestones: Milestone 4: Post 1.0 releases, Backlog Jun 6, 2018
@bbondy
Copy link
Member Author

bbondy commented Jun 6, 2018

repuposing this one to be only for tabs and to backlog since per window is fine for now.

@rebron rebron added the priority/P4 Planned work. We expect to get to it "soon". label Oct 5, 2018
@tildelowengrimm tildelowengrimm added priority/P5 Not scheduled. Don't anticipate work on this any time soon. and removed priority/P4 Planned work. We expect to get to it "soon". labels Oct 30, 2018
@tildelowengrimm tildelowengrimm modified the milestones: 1.x Backlog, Dupe / Invalid / Not actionable Nov 15, 2018
@oshanz oshanz mentioned this issue Dec 20, 2019
Closed
@bbondy bbondy removed this from the Dupe / Invalid / Not actionable milestone May 30, 2020
@iefremov iefremov mentioned this issue Nov 27, 2020
Closed
@bridiver bridiver mentioned this issue Mar 31, 2022
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
browser-laptop-parity closed/invalid closed/wontfix feature/tor priority/P5 Not scheduled. Don't anticipate work on this any time soon.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@tildelowengrimm @bbondy @bsclifton @rebron @riastradh-brave