Open Bug 1146495 Opened 11 years ago Updated 3 years ago

Private browsing indicator not shown when startup with "-private" command line switch

Categories

(Firefox :: Private Browsing, defect)

36 Branch
x86
Windows 7
defect

Tracking

()

People

(Reporter: towlyhk-mozilla, Unassigned)

Details

User Agent: Mozilla/5.0 (Windows NT 6.1; rv:36.0) Gecko/20100101 Firefox/36.0 Build ID: 20150320202338 Steps to reproduce: Add "-private" switch to firefox shortcut. Start firefox by the double click the shortcut. Actual results: Firefox start with the "You're browsing privately" tab. But the private browsing window indicator is not shown. Expected results: The purple private browsing window indicator should be shown on the right hand side of the titlebar.
Component: Untriaged → Private Browsing
This is an intentional choice - we explicitly check in http://mxr.mozilla.org/mozilla-central/source/toolkit/modules/PrivateBrowsingUtils.jsm?force=1#54 for whether the `-private` flag was present at startup, and we base various UI decisions on that check.
So (In reply to Josh Matthews [:jdm] from comment #1) > This is an intentional choice - we explicitly check in > http://mxr.mozilla.org/mozilla-central/source/toolkit/modules/ > PrivateBrowsingUtils.jsm?force=1#54 for whether the `-private` flag was > present at startup, and we base various UI decisions on that check. what is presented by the title is confirmed. Please change status either to VERIFIED or to INVALID. Any way, why any UI decisions especially for private browsing are based on command line and private browsing UI is differentiate based on that? People (like me) get confused if the private browsing window does not show the indicator. Personally I opened many new private browsing windows before I understand that is not possible to have a real private browsing window from one started from command line. Initially I thought was some "phishing" page.
I suspect the code I previously linked is conflating our "always private browsing mode" with "first window opened is a private window", which is not what we should be doing.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.