Closed
Bug 651213
Opened 13 years ago
Closed 13 years ago
about:home loses unrestored session after restart
Categories
(Firefox :: Session Restore, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 637148
Tracking | Status | |
---|---|---|
firefox5 | --- | affected |
People
(Reporter: GPHemsley, Unassigned)
Details
(Keywords: regression)
This appears to be a regression from Firefox 4. In the past, about:sessionrestore was restored as any other tab if it was unrestored upon restart. With the new about:home, Session Restore is incorporated into the new homepage as a button. If that button is not pressed before a restart, the data appears to be lost. (Manually going to about:sessionrestore shows only an additional about:home tab.) I was running a days-old instance of Aurora 5 when I restarted to update. (It hanged on shutdown, but that happens a lot, so I don't think it's related. I forced quit it and reopened it manually.) Upon first restart, the about:home page showed a Session Restore button. However, since I knew I had updated to an obsolete build, so I manually checked for updates and restarted again. When Aurora loaded the second time, there was no Session Restore button. Instead, there was an about:home app tab (which I had created manually in the original session) and a second regular about:home tab. In addition, there are no backup session restore files that might have the session data in it. (There is a sessionrestore.bak, but it only contains data for the two about:home tabs.) I don't know what the cause is, but I suspect it is related to the new about:home interface for session restore.
Limi, is this bug 628043? This is an intend train, correct? Gordon, can you file a different bug for the shutdown hangs you are seeing?
tracking-firefox6:
? → ---
Reporter | ||
Comment 2•13 years ago
|
||
(In reply to comment #1) > Limi, is this bug 628043? This is an intend train, correct? For the record, I'm on Mac. Not sure if that matters. > Gordon, can you file a different bug for the shutdown hangs you are seeing? Filed as bug 651319, but I don't know how helpful it is. (Also, I filed it in Firefox :: General; not sure if there's a better place for it.)
Comment 3•13 years ago
|
||
(In reply to comment #0) > This appears to be a regression from Firefox 4. This isn't a regression from 4. Nothing has changed around that for 5 so we probably shouldn't be tracking it, right? (In reply to comment #1) > Limi, is this bug 628043? This is an intend train, correct? This isn't that bug. It's really bug 637148 (I'll leave unduped for now).
Reporter | ||
Comment 4•13 years ago
|
||
(In reply to comment #3) > (In reply to comment #0) > > This appears to be a regression from Firefox 4. > > This isn't a regression from 4. Nothing has changed around that for 5 so we > probably shouldn't be tracking it, right? Oh, shoot, you're right. Forgot about:home came with Fx4. It came late in the game there, though, didn't it? (My head's all confused because I'd been using the betas for a while.) > (In reply to comment #1) > > Limi, is this bug 628043? This is an intend train, correct? > > This isn't that bug. It's really bug 637148 (I'll leave unduped for now). I'll do the deed.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → DUPLICATE
Updated•13 years ago
|
tracking-firefox5:
+ → ---
You need to log in
before you can comment on or make changes to this bug.
Description
•