Closed Bug 813533 Opened 7 years ago Closed 7 years ago

Private browsing doesn't work correctly after opening new window

Categories

(Firefox :: Private Browsing, defect)

x86
macOS
defect
Not set

Tracking

()

VERIFIED FIXED
Firefox 20
Tracking Status
firefox17 --- unaffected
firefox18 --- unaffected
firefox19 + verified
firefox20 + verified

People

(Reporter: tetsuharu, Assigned: jdm)

References

Details

(Keywords: regression)

Attachments

(2 files, 1 obsolete file)

Enviroment:
*Firefox Nightly 20.
 http://hg.mozilla.org/mozilla-central/rev/bc69705c162d
*Intel Mac OS X 10.8

Step to reproduce:
1) open window 'A' & turn on Private-browsing.
2) close window 'A' (but keep running Firefox in dock).
3) open a new window 'B'.
4) open a URL in window 'B'.

Result:
The opened URL is recorded in browsing history.

More info:
This bug appears in Nightly 19, after http://hg.mozilla.org/mozilla-central/rev/a761bfc192b5. (Sorry, I could not report this bug immediately.)
We will need to land a patch which will fix this to aurora 19 code base.
This got in-person r+ from ehsan, so I'm going to land it.
To fix this on Aurora, I'll back out bug 795556.
Josh can you please attach the backout patch for approval?  Thanks!
Assignee: nobody → josh
Attached patch Back out bug 795556 patch #2. (obsolete) — Splinter Review
[Approval Request Comment]
Bug caused by (feature/regressing bug #): 795556
User impact if declined: Non-private windows (and associated behaviour) while in private mode in certain limited situations.
Testing completed (on m-c, etc.): Restoring previous behaviour by backing out patch that changed it.
Risk to taking this patch (and alternatives if risky): None. The code being restored ensured that all windows were correctly marked as private if PB mode was enabled.
String or UUID changes made by this patch: None.
Attachment #683708 - Flags: review?(ehsan)
Attachment #683708 - Flags: approval-mozilla-aurora?
Attachment #683708 - Attachment is obsolete: true
Attachment #683708 - Flags: review?(ehsan)
Attachment #683708 - Flags: approval-mozilla-aurora?
Comment on attachment 683713 [details] [diff] [review]
Back out bug 795556 patch #2.

[Approval Request Comment]
Bug caused by (feature/regressing bug #): 795556
User impact if declined: Non-private windows (and associated behaviour) while in private mode in certain limited situations.
Testing completed (on m-c, etc.): Restoring previous behaviour by backing out patch that changed it.
Risk to taking this patch (and alternatives if risky): None. The code being restored ensured that all windows were correctly marked as private if PB mode was enabled.
String or UUID changes made by this patch: None.
Attachment #683713 - Flags: approval-mozilla-aurora?
https://hg.mozilla.org/mozilla-central/rev/8f847258636a
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 20
Umm...  From commit log, this patch have been landed already.
But In today's nightly build (http://hg.mozilla.org/mozilla-central/rev/4f19e7fd8bea), this has not fixed yet...
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
I tried today's nightly and it works fine for me. Here are the steps I followed:

1) Enter PB session
2) Close all open windows, leaving the app open in the dock
3) Open a new window, visit an unvisited page

The new window opens to about:privatebrowsing, and the page I visit doesn't show up in the history.
Status: REOPENED → RESOLVED
Closed: 7 years ago7 years ago
Resolution: --- → FIXED
Comment on attachment 683713 [details] [diff] [review]
Back out bug 795556 patch #2.

[Triage Comment]
Low risk backout, approving for Aurora 19.
Attachment #683713 - Flags: approval-mozilla-aurora? → approval-mozilla-aurora+
Blocks: 795556
Keywords: regression
Backed out: https://hg.mozilla.org/releases/mozilla-aurora/rev/fe01134efd58

Josh claims that he has a patch that actually builds:


philor
ehsan: not enough backout on aurora? needed-clobber?
dbaron
ehsan, red on aurora... oh
ehsan
philor: oh noes, that backout patch is broken
jprmc has left IRC (Input/output error)
jdm
ehsan: are you talking about the pb-related backout?
jdm
because yeah, I have a local patch which actually builds
ehsan
yeah
ehsan
good
ehsan
please land it ;)
17:09 jdm
so demanding
(In reply to Josh Matthews [:jdm] from comment #10)
> I tried today's nightly and it works fine for me. Here are the steps I
> followed:
> 
> 1) Enter PB session
> 2) Close all open windows, leaving the app open in the dock
> 3) Open a new window, visit an unvisited page
> 
> The new window opens to about:privatebrowsing, and the page I visit doesn't
> show up in the history.

I find the special case which has not been fixed yet.
So In step 3), if we opened a new window with 'click dock icon', the page I visit show up in the history.

If we opened a new window with 'dock-context-menu or menu-bar', this bug has been fixed in today's nightly.

So should I file a new bug?
(In reply to comment #15)
> (In reply to Josh Matthews [:jdm] from comment #10)
> > I tried today's nightly and it works fine for me. Here are the steps I
> > followed:
> > 
> > 1) Enter PB session
> > 2) Close all open windows, leaving the app open in the dock
> > 3) Open a new window, visit an unvisited page
> > 
> > The new window opens to about:privatebrowsing, and the page I visit doesn't
> > show up in the history.
> 
> I find the special case which has not been fixed yet.
> So In step 3), if we opened a new window with 'click dock icon', the page I
> visit show up in the history.
> 
> If we opened a new window with 'dock-context-menu or menu-bar', this bug has
> been fixed in today's nightly.
> 
> So should I file a new bug?

Yes, please.  Thanks a lot!
I confirm the fix is verified on FF 19b4 on Mac OS 10.8. I was not able to reproduce the issue mentioned by Tetsuharu in Comment 15. Is your issue from Comment 15 intermittent ?
Verified fixed on FF 20.b1:

Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:20.0) Gecko/20100101 Firefox/20.0
Verified fixed on FF 20.b5
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.