Open Bug 647401 Opened 13 years ago Updated 2 years ago

tabs from closed window are restored when opening new window with history open

Categories

(Firefox :: General, defect)

4.0 Branch
x86
Windows XP
defect

Tracking

()

UNCONFIRMED

People

(Reporter: chris, Unassigned)

Details

User-Agent:       Mozilla/5.0 (Windows NT 6.1; WOW64; rv:2.0) Gecko/20100101 Firefox/4.0
Build Identifier: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:2.0) Gecko/20100101 Firefox/4.0

If you have the history window open, and close your only browser window, then open a new window - all the tabs from the just closed window are restored.


Reproducible: Always

Steps to Reproduce:
1. Open single browser window with some tabs
2. Open history window
3. Close browser window
4. Open new browser window
Actual Results:  
Tabs from the closed window are loaded

Expected Results:  
Opened a new window to the home page
Version: unspecified → 4.0 Branch
Confirmed on Mozilla/5.0 (Windows NT 6.1; rv:2.2a1pre) Gecko/20110407 Firefox/4.2a1pre
I could reproduce what was described above on:
Mozilla/5.0 (Windows NT 6.1; rv:2.2a1pre) Gecko/20110407 Firefox/4.2a1pre

But it's unclear whether it is a bug or not; if the history window is still open (belonging to a Firefox instance) it is presumable that if closing and reopening a window would keep the content from that instance.

Remaining Unconfirmed. Proposing it as invalid.
OS: Windows 7 → Windows XP
(In reply to comment #2)
> I could reproduce what was described above on:
> Mozilla/5.0 (Windows NT 6.1; rv:2.2a1pre) Gecko/20110407 Firefox/4.2a1pre
> 
> But it's unclear whether it is a bug or not; if the history window is still
> open (belonging to a Firefox instance) it is presumable that if closing and
> reopening a window would keep the content from that instance.
> 
> Remaining Unconfirmed. Proposing it as invalid.

By that logic, the same behaviour should exist when closing and reopening a window when the instance is kept alive by another window, and not just the history window.
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.