Open
Bug 1118073
Opened 9 years ago
Updated 2 years ago
Second Tab Ignored When Using --private-window From The CLI
Categories
(Firefox :: Private Browsing, defect)
Tracking
()
UNCONFIRMED
People
(Reporter: junkfoodjunki, Unassigned)
References
Details
User Agent: Mozilla/5.0 (X11; Linux i686; rv:34.0) Gecko/20100101 Firefox/34.0 Build ID: 20141201180357 Steps to reproduce: When I run firefox --private-window https://duckduckgo.com https://crunchbang.org Actual results: Firefox opens duckduckgo.com in a private window but crunchbang.org in a normal window Expected results: I would of exected firefox to open both URI's in the same private window
Comment 1•9 years ago
|
||
Reproduced with 2015-01-12-03-02-01-mozilla-central-firefox-37.0a1.ru.linux-x86_64 Also, "firefox --private-window https://duckduckgo.com --private-window https://crunchbang.org" loads only https://duckduckgo.com in a private window. Same with "-private-window" (https://developer.mozilla.org/en-US/docs/Mozilla/Command_Line_Options).
Blocks: 960600
QA Whiteboard: [bugday-20140112]
Updated•9 years ago
|
QA Whiteboard: [bugday-20140112] → [bugday-20150112]
Updated•9 years ago
|
Component: Untriaged → Private Browsing
Comment 2•9 years ago
|
||
The difference is in http://mxr.mozilla.org/mozilla-central/source/browser/components/nsBrowserContentHandler.js#403 vs http://mxr.mozilla.org/mozilla-central/source/browser/components/nsBrowserContentHandler.js#346 . The latter has a while loop, while the former doesn't, which explains the behaviour that Aleksej is seeing. I'm not sure if solving the original issue (ie. one --private-window argument and a bunch of URLs) is feasible, however.
I get this as well. Even if I press the + for a new tab, it opens in a non-private tab. On the same machine, I have a working account that that gives me a (Private Browsing) in the title bar and works as expected. I think it is related to bug 1113573 Private browsing not working on some computers. $1: firefox --private-window WARNING: content window passed to PrivateBrowsingUtils.isWindowPrivate. Use isContentWindowPrivate instead (but only for frame scripts). pbu_isWindowPrivate@resource://gre/modules/PrivateBrowsingUtils.jsm:25:14 @about:privatebrowsing:25:12 WARNING: content window passed to PrivateBrowsingUtils.isWindowPrivate. Use isContentWindowPrivate instead (but only for frame scripts). pbu_isWindowPrivate@resource://gre/modules/PrivateBrowsingUtils.jsm:25:14 @about:privatebrowsing:50:14 $1: firefox -private WARNING: content window passed to PrivateBrowsingUtils.isWindowPrivate. Use isContentWindowPrivate instead (but only for frame scripts). pbu_isWindowPrivate@resource://gre/modules/PrivateBrowsingUtils.jsm:25:14 @about:privatebrowsing:25:12 WARNING: content window passed to PrivateBrowsingUtils.isWindowPrivate. Use isContentWindowPrivate instead (but only for frame scripts). pbu_isWindowPrivate@resource://gre/modules/PrivateBrowsingUtils.jsm:25:14 @about:privatebrowsing:50:14
This issue is still reproducible on Firefox 58. Is there someone going to fix this?
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•