Closed
Bug 883577
Opened 11 years ago
Closed 11 years ago
Last page visited should not include private browsing windows
Categories
(SeaMonkey :: UI Design, defect)
SeaMonkey
UI Design
Tracking
(seamonkey2.19 fixed, seamonkey2.20 fixed, seamonkey2.21 fixed)
RESOLVED
FIXED
seamonkey2.21
People
(Reporter: neil, Assigned: neil)
References
(Blocks 1 open bug)
Details
Attachments
(2 files)
1021 bytes,
patch
|
iannbugzilla
:
review+
philip.chee
:
feedback+
|
Details | Diff | Splinter Review |
1015 bytes,
patch
|
Callek
:
approval-comm-aurora+
Callek
:
approval-comm-beta+
|
Details | Diff | Splinter Review |
Steps to reproduce problem: 1. Configure a new browser window (or tab) to open the last page visited 2. Open a private window 3. Visit a page 4. Open a new browser window (or tab) Actual result: page visited in private window opens
Assignee | ||
Comment 1•11 years ago
|
||
Note: Patch includes relevant change from bug 883532.
Assignee: nobody → neil
Status: NEW → ASSIGNED
Attachment #763172 -
Flags: review?(iann_bugzilla)
Attachment #763172 -
Flags: feedback?(philip.chee)
Comment 2•11 years ago
|
||
Comment on attachment 763172 [details] [diff] [review] Proposed patch Tested with the STR in Comment 0. f=me. > // nsIWebProgressListener partial implementation > onLocationChange: function(aWebProgress, aRequest, aLocation, aFlags) > { > if (aWebProgress.DOMWindow.top == aWebProgress.DOMWindow && I think we can use aWebProgress.isTopLevel here thanks to Bug 666801. [spotted a few other places where we could use .isTopLevel]
Attachment #763172 -
Flags: feedback?(philip.chee) → feedback+
Attachment #763172 -
Flags: review?(iann_bugzilla) → review+
(In reply to Philip Chee from comment #2) > > if (aWebProgress.DOMWindow.top == aWebProgress.DOMWindow && > I think we can use aWebProgress.isTopLevel here thanks to Bug 666801. > [spotted a few other places where we could use .isTopLevel] Logged bug 884132 to cover that.
Assignee | ||
Comment 4•11 years ago
|
||
Pushed comm-central changeset c676fc4b9ae0.
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Target Milestone: --- → seamonkey2.21
Assignee | ||
Comment 5•11 years ago
|
||
[Approval Request Comment] User impact if declined: Privacy leak Risk to taking this patch (and alternatives if risky): Low
Attachment #765650 -
Flags: approval-comm-beta?
Attachment #765650 -
Flags: approval-comm-aurora?
Updated•11 years ago
|
Attachment #765650 -
Flags: approval-comm-beta?
Attachment #765650 -
Flags: approval-comm-beta+
Attachment #765650 -
Flags: approval-comm-aurora?
Attachment #765650 -
Flags: approval-comm-aurora+
Assignee | ||
Comment 6•11 years ago
|
||
Forgot the bug#. Oops. https://hg.mozilla.org/releases/comm-aurora/rev/0be1bcbc416c http://hg.mozilla.org/releases/comm-beta/rev/049349753f15
status-seamonkey2.19:
--- → fixed
status-seamonkey2.20:
--- → fixed
status-seamonkey2.21:
--- → fixed
You need to log in
before you can comment on or make changes to this bug.
Description
•