Open Bug 1096726 Opened 8 years ago Updated 1 month ago

Firefox 32 or higher refuses to restore session files from older versions

Categories

(Firefox :: Session Restore, defect, P3)

32 Branch
All
Windows XP
defect

Tracking

()

UNCONFIRMED

People

(Reporter: SlimShadyBSB, Unassigned)

Details

-Install Firefox 32 or higher
-Copy sessionstore.js from any GOOD version of Firefox (I tested with files from FF2, FF3, and FF30)
-Paste file into %AppData%
-Open Firefox
-Firefox opens onto Firefox's default "home pages" with no session listed
-Typing about:sessionrestore into the URL bar shows an empty session restore page.

OR:

-Install Firefox 32 or higher
-Also install Firefox 3 or another GOOD version of Firefox into a different Program Files folder
-Open the older version and use the Web
-Close or end task of the older version
-Open Firefox 32 or higher
-Firefox opens onto Firefox's default "home pages" with no session listed
-Typing about:sessionrestore into the URL bar shows an empty session restore page.

Note that this issue may have started in either 31 or 32 (an automatic update may have been made to my software without my knowledge or express permission), however, the issue does persist in 33.  A brand new Mozilla folder was created, renaming the old one.  The issue continued to persist in both FF32 and FF33.

Sorry for the weird formatting.  Apparently putting in all the options changes the submission form to a normal form, so I still had the "stupid user form" text in Notepad and just copied and added a little.
Priority: -- → P2
Severity: major → critical
Moving to p3 because no activity for at least 1 year(s).
See https://github.com/mozilla/bug-handling/blob/master/policy/triage-bugzilla.md#how-do-you-triage for more information
Priority: P2 → P3
Moving to p3 because no activity for at least 1 year(s).
See https://github.com/mozilla/bug-handling/blob/master/policy/triage-bugzilla.md#how-do-you-triage for more information

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 → --
You need to log in before you can comment on or make changes to this bug.