Closed Bug 835440 Opened 12 years ago Closed 2 months ago

All tabs lost when closing window while view source window is still open

Categories

(Firefox :: Session Restore, defect)

Product:
Firefox
Component:
Session Restore
Platform:
x86_64
Windows Server 2003
Type:
defect

Tracking

()

Status:
RESOLVED INVALID

People

(Reporter: jab_creations, Unassigned)

References

(Blocks 1 open bug)

Details

(Keywords: dataloss)

Firefox does not visually update after coming out of sleep so I have been closing it and reopening it with tabs/windows restored when Firefox restarts. I had previously been working with source code in a View Source window. When I closed the main window I did not realize that the view source window was still open. I then proceeded to open Firefox... (Shortcut)... "C:\MEDIA\INTERNET\Mozilla Firefox 17.0\firefox.exe" -P "Mozilla Firefox 17.0 ESR" Which then loaded with the same number of tabs (it seemed) that were all empty. ALL of my tabs and tab groups were LOST! Opening the shortcut Firefox should have told me that the profile was still open and to first close all relevant tabs! Because I have "don't load tabs until I select them" I can not simply go back to the history. I attempted to restore tabs through the History menu --> Tabs from other Computers though sync had updated and got rid of all my tabs!
Component: Tabbed Browser → Session Restore
This is really a combination of issues, that I suspect is not fixable by session restore. (In reply to John A. Bilicki III from comment #0) > Firefox does not visually update after coming out of sleep so I have been > closing it and reopening it with tabs/windows restored when Firefox restarts. problem #1 - not session restore > I had previously been working with source code in a View Source window. When > I closed the main window I did not realize that the view source window was > still open. I then proceeded to open Firefox... > (Shortcut)... > "C:\MEDIA\INTERNET\Mozilla Firefox 17.0\firefox.exe" -P "Mozilla Firefox > 17.0 ESR" > Which then loaded with the same number of tabs (it seemed) that were all > empty. I'm surprised it loaded any > ALL of my tabs and tab groups were LOST! > > Opening the shortcut Firefox should have told me that the profile was still > open and to first close all relevant tabs! problem #2 - never has, and never will happen if developers who have decided for man years regarding how firefox shortcuts should behave with an open firefox instance. iirc there are one or more WONTFIX bugs about changing this behavior. > Because I have "don't load tabs until I select them" I can not simply go > back to the history. irrc that doesn't (or shouldn't) affect your ability to restore tabs That said, is behavior different if you use a newer version of Firefox?
Flags: needinfo?(jab_creations)
Tested Gecko/20100101 Firefox/27.0, opened second tab, viewed source, closed main window and THEN view source window. Opened Firefox again and only the homepage opened.
Flags: needinfo?(jab_creations)
similar issue reported in bug 654951 such an issue was fixed a long time ago in Firefox 3.6a1 via bug 354894
Keywords: dataloss

In the process of migrating remaining bugs to the new severity system, the severity for this bug cannot be automatically determined. Please retriage this bug using the new severity system.

Severity: critical → --

The severity field is not set for this bug.
:dao, could you have a look please?

For more information, please visit BugBot documentation.

Flags: needinfo?(dao+bmo)

It sounds like this is counter-intuitive, but technically "expected" behavior. I want to see if this still reproduces but its likely any work to improve the experience here will happen in another bug.

Flags: needinfo?(dao+bmo)

The severity field is not set for this bug.
:dao, could you have a look please?

For more information, please visit BugBot documentation.

Flags: needinfo?(dao+bmo)

So the window and tabs closed in comment #0 would have been listed in the "Recently closed windows". Because the "view-source" window was still open, the session had not yet ended and so session restore didn't occur.

I agree that this is confusing and something we have been wanting to change but its not a bug we'll fix here.

Status: UNCONFIRMED → RESOLVED
Closed: 2 months ago
Flags: needinfo?(dao+bmo)
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.