Open Bug 1521372 Opened 9 months ago Updated 9 months ago

-private is effective for one window; not permanent private browsing

Categories

(Firefox :: Private Browsing, defect, P3)

63 Branch
defect

Tracking

()

UNCONFIRMED

People

(Reporter: grahamperrin, Unassigned)

References

()

Details

User Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:56.0; Waterfox) Gecko/20100101 Firefox/56.2.6

Steps to reproduce:

  1. firefox -private

  2. observe the private window

  3. new window

Actual results:

  1. no hint that browsing is private (bug 1048286) and truly, it is not private

  2. visit a non-historical site

  3. the visited site is in history.

Expected results:

  1. permanent private browsing.

Bug first observed with Firefox 64.0.2 on FreeBSD-CURRENT,

grahamperrin@momh167-gjp4-8570p:~ % date ; uname -v
Sun 20 Jan 2019 11:30:14 GMT
FreeBSD 13.0-CURRENT r343023 GENERIC-NODEBUG
grahamperrin@momh167-gjp4-8570p:~ % pkg query '%o %v %R' firefox
www/firefox 64.0.2,1 FreeBSD
grahamperrin@momh167-gjp4-8570p:~ %

Reproduced with 63.0 in Lubuntu 18.10.

Reference: https://developer.mozilla.org/docs/Mozilla/Command_Line_Options

Component: Untriaged → Private Browsing
Priority: -- → P3

Is this a regression from an earlier version of Firefox? If so, could you use http://mozilla.github.io/mozregression/ to help track down when it regressed?

Flags: needinfo?(grahamperrin)

Is this a regression from an earlier version of Firefox?

Given the 2014-08-04 reopening of bug 1048286 for the indicator, I assume that (yes) permanent private browsing did work, albeit without its indicator, around the time of Firefox 31 (released a little earlier, 2014-07-22).

There's a comparable bug with Waterfox https://github.com/MrAlex94/Waterfox/issues/844, version 56.0 of which was based on Firefox 56.0.2, so (loosely) I guess that the regression occurred somewhere between 31 and 56.

mozregression

I used it only once before, on a very slow Mac. I'll see how I get on with Lubuntu in a virtual machine.

Flags: needinfo?(grahamperrin)

/me hits mozregression bug 1503358

You need to log in before you can comment on or make changes to this bug.