Remove extensions.allowPrivateBrowsingByDefault preference
Categories
(WebExtensions :: General, task, P3)
Tracking
(firefox91 verified)
Tracking | Status | |
---|---|---|
firefox91 | --- | verified |
People
(Reporter: mixedpuppy, Assigned: soniasingla, Mentored)
References
(Blocks 1 open bug)
Details
(Keywords: good-first-bug)
Attachments
(2 files)
Comment 2•4 years ago
|
||
is this issue still open? if yes, can I attempt it, please?
charlesanita403@gmail.com
Comment 3•4 years ago
|
||
Thanks for your interest in this bug. I've clarified the title, Shane will follow up with a comment.
Reporter | ||
Comment 4•4 years ago
|
||
I apologize for missing the question. Are you still interested in taking this?
Reporter | ||
Updated•4 years ago
|
Reporter | ||
Comment 5•4 years ago
|
||
No response, clearing need info's.
Assignee | ||
Comment 6•4 years ago
|
||
Updated•4 years ago
|
extensions.allowPrivateBrowsingByDefault
is true by default in Tor Browser, differing from Firefox.
Comment 8•4 years ago
|
||
The Tor Browser uses permanent private browsing mode by default (via pref("browser.privatebrowsing.autostart", true);
). We could look into automatically enabling extensions in permanent private browsing mode (bug 1585431). That work does not need to block this bug, since Tor builds on ESR anyway.
Reporter | ||
Comment 9•4 years ago
|
||
Comment 10•4 years ago
|
||
Hey Sonia, just wanted to check in. :) Are you still working on this bug?
Comment 11•4 years ago
|
||
Hey Sonia, just another friendly check in on this issue. :) How's it going?
Assignee | ||
Comment 12•4 years ago
|
||
Updating it now, thanks for checking :)
Comment 13•4 years ago
|
||
This good-first-bug hasn't had any activity for 2 months, it is automatically unassigned.
For more information, please visit auto_nag documentation.
Updated•4 years ago
|
Comment 14•4 years ago
|
||
Comment 15•4 years ago
|
||
bugherder |
Comment 16•4 years ago
|
||
Hello,
Verified the fix on the latest Nightly (91.0a1/20210603094827) under Windows x64 and Ubuntu 16.04 LTS.
Compared the existence of the pref in about:config between Nightly and Release. On Release the pref still exists and is set to false, while on Nightly it is no longer available, confirming the fix. For further details, please see the attached screenshot.
Comment 17•4 years ago
|
||
Comment 18•3 years ago
|
||
Hi,
by removing this preference there is no more way to programmatically turn on this setting in testing environment with WebDriver.
I have web extension that talks with my app over WebDriver and controls proxy in browser. It is broken currently as extension cant call browser.proxy.settings.set api without private browsing permission and I have no way to set that permission from geckodriver.
Comment 19•3 years ago
|
||
(In reply to Boris Prpic from comment #18)
Hi,
by removing this preference there is no more way to programmatically turn on this setting in testing environment with WebDriver.
I have web extension that talks with my app over WebDriver and controls proxy in browser. It is broken currently as extension cant call browser.proxy.settings.set api without private browsing permission and I have no way to set that permission from geckodriver.
Could you file a new bug for this issue? Please include relevant information, such as a set of (minimal) steps to reproduce the issue.
Comment 20•3 years ago
|
||
(In reply to Rob Wu [:robwu] from comment #19)
(In reply to Boris Prpic from comment #18)
Hi,
by removing this preference there is no more way to programmatically turn on this setting in testing environment with WebDriver.
I have web extension that talks with my app over WebDriver and controls proxy in browser. It is broken currently as extension cant call browser.proxy.settings.set api without private browsing permission and I have no way to set that permission from geckodriver.
Could you file a new bug for this issue? Please include relevant information, such as a set of (minimal) steps to reproduce the issue.
OK. Here: https://bugzilla.mozilla.org/show_bug.cgi?id=1729315
Description
•