Clicking the "Close private tabs?" notification of Tor Browser for Android only closes all webpage opened, and browser data is not cleaned
🐞 Bug Report
Reproduction steps
- Open Tor Browser for Android, connect to Tor network.
- Visit any website. (IMPORTANT: Notification won't appear if no website is opened.) 2.5. (Extra) Install a Cookie manager extension (e.g. Cookie quick manager) and make sure the website has some cookies stored on this browser.
- Click the "Close private tabs?" notification. 3.5. (Extra) Open the Cookie manager extension to see if cookies are cleared.
Cookie Quick Manager: https://addons.mozilla.org/en-US/firefox/addon/cookie-quick-manager/
Expected behaviour
The browser closed with all data wiped.
Actual behaviour
The browser act like it just connected to Tor network, and cookie quick manager shows all cookies stored in previous session.
Related issues
Probably related to issues/#43565 (closed) , the description seems familiar.
Bookkeeping
- Browser version: Tor Browser Alpha 14.5a6(128.9.0esr)
- Browser channel:
-
Release -
Alpha -
Nightly
-
- Distribution method:
-
Installer/archive from torproject.org -
tor-browser-launcher -
homebrew -
other (please specify): Guardian Project
-
- Operating System:
-
Windows -
macOS -
Linux -
Android -
Tails -
Other (please specify):
-
- Operating System Version: Appeared on Android 13, reproduced on Android 15 (LineageOS)
Browser UI language
English (US)
(By the way, no such thing as about:preferences or about:config exists in Tor Browser for Android, please consider updating bug reporting template.)
Have you modified any of the settings in about:preferences or about:config? If yes, which ones?
"Security Level" to "safer".
Do you have any extra extensions installed?
Yes, to demonstrate this bug.
Troubleshooting
Does this bug occur in a fresh installation?
Yes.
Is this bug new? If it is a regression, in which version of the browser did this bug first appear?
I don't know. But this bug didn't occur in Tor Browser for Android stable (14.0.9).
Does this bug occur in the Alpha release channel?
Yes.
Does this bug occur in Firefox ESR (Desktop only)?
Not applicable.
Does this bug occur in Firefox Rapid Release?
Not applicable.
Edited by anon_tokyo