This repository has been archived by the owner on Dec 11, 2019. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 970
Feature Request: Default Private Browsing / Private Tab Sessions #8963
Labels
addressed-with-brave-core
Needs confirmation, but this issue may be resolved with Brave Core.
feature/private-tabs
privacy
settings
shell-integration
Integrating brave with OS-level UI features.
stale
Comments
diracdeltas
added a commit
that referenced
this issue
Sep 7, 2017
partial fix for #6684 and #8963 TODO: Either the private tab sessions should be cleared and revert back to private session 1 when the last private tab is closed, or we need a private tab session manager menu. Currently the session will keep incrementing until the browser restarts. Test Plan: 1. open private tab 2. in the private tab, go to a site that requires login 3. login, then open a link from that site in a new private tab 4. you should also be logged in in the second private tab 5. open a new private tab 6. go to the same site. you should not be logged in.
diracdeltas
added a commit
that referenced
this issue
Sep 7, 2017
partial fix for #6684 and #8963 TODO: Either the private tab sessions should be cleared and revert back to private session 1 when the last private tab is closed, or we need a private tab session manager menu. Currently the session will keep incrementing until the browser restarts. Test Plan: 1. open private tab 2. in the private tab, go to a site that requires login 3. login, then open a link from that site in a new private tab 4. you should also be logged in in the second private tab 5. open a new private tab 6. go to the same site. you should not be logged in.
8 tasks
diracdeltas
added a commit
that referenced
this issue
Sep 11, 2017
partial fix for #6684 and #8963 TODO: Either the private tab sessions should be cleared and revert back to private session 1 when the last private tab is closed, or we need a private tab session manager menu. Currently the session will keep incrementing until the browser restarts. Test Plan: 1. open private tab 2. in the private tab, go to a site that requires login 3. login, then open a link from that site in a new private tab 4. you should also be logged in in the second private tab 5. open a new private tab 6. go to the same site. you should not be logged in.
diracdeltas
added a commit
that referenced
this issue
Oct 11, 2017
partial fix for #6684 and #8963 TODO: Either the private tab sessions should be cleared and revert back to private session 1 when the last private tab is closed, or we need a private tab session manager menu. Currently the session will keep incrementing until the browser restarts. Test Plan: 1. open private tab 2. in the private tab, go to a site that requires login 3. login, then open a link from that site in a new private tab 4. you should also be logged in in the second private tab 5. open a new private tab 6. go to the same site. you should not be logged in.
diracdeltas
added a commit
that referenced
this issue
Oct 25, 2017
partial fix for #6684 and #8963 TODO: Either the private tab sessions should be cleared and revert back to private session 1 when the last private tab is closed, or we need a private tab session manager menu. Currently the session will keep incrementing until the browser restarts. Test Plan: 1. open private tab 2. in the private tab, go to a site that requires login 3. login, then open a link from that site in a new private tab 4. you should also be logged in in the second private tab 5. open a new private tab 6. go to the same site. you should not be logged in.
diracdeltas
added a commit
that referenced
this issue
Dec 4, 2017
partial fix for #6684 and #8963 TODO: Either the private tab sessions should be cleared and revert back to private session 1 when the last private tab is closed, or we need a private tab session manager menu. Currently the session will keep incrementing until the browser restarts. Test Plan: 1. open private tab 2. in the private tab, go to a site that requires login 3. login, then open a link from that site in a new private tab 4. you should also be logged in in the second private tab 5. open a new private tab 6. go to the same site. you should not be logged in.
diracdeltas
added a commit
that referenced
this issue
Jan 2, 2018
partial fix for #6684 and #8963 TODO: Either the private tab sessions should be cleared and revert back to private session 1 when the last private tab is closed, or we need a private tab session manager menu. Currently the session will keep incrementing until the browser restarts. Test Plan: 1. open private tab 2. in the private tab, go to a site that requires login 3. login, then open a link from that site in a new private tab 4. you should also be logged in in the second private tab 5. open a new private tab 6. go to the same site. you should not be logged in.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
addressed-with-brave-core
Needs confirmation, but this issue may be resolved with Brave Core.
feature/private-tabs
privacy
settings
shell-integration
Integrating brave with OS-level UI features.
stale
Did you search for similar issues before submitting this one?
Describe the issue you encountered:
The following options (and the behaviors described) added to the security tab can prevent this:
Additionally, useful context menu integration from the desktop/win explorer:
Platform and Version information from about:brave
Brave 0.15.2
rev af7ef42
Muon 2.58.9
libchromiumcontent 58.0.3029.96
V8 5.8.283.37
Node.js 7.9.0
Update Channel dev
os.platform win32
os.release 10.0.14393
os.arch x64
Steps to reproduce:
Expected result:
Will the steps above reproduce in a fresh profile? If not what other info can be added?
yes
Is this an issue in the currently released version?
yes
Can this issue be consistently reproduced?
yes
Extra QA steps:
Related information:
Included context menu suggestion because implementing those first could make most of these features a quick win. Private Tab Sessions may require much more technical involvement.
The text was updated successfully, but these errors were encountered: