After crash pinned tabs are restored, but non-pinned tabs are not. See about:home, with the option restore tabs from a previous session.
Categories
(Firefox :: Session Restore, defect)
Tracking
()
People
(Reporter: mccr8, Unassigned)
References
(Blocks 1 open bug)
Details
| Reporter | ||
Comment 1•10 years ago
|
||
| Reporter | ||
Comment 3•10 years ago
|
||
| Reporter | ||
Comment 4•10 years ago
|
||
Comment 5•9 years ago
|
||
| Reporter | ||
Comment 6•9 years ago
|
||
Comment 7•6 years ago
|
||
It's reproducible to me, Firefox 66.0.1 (64-bit) on Linux.
Comment 8•6 years ago
|
||
But in my case the pinned tabs do not restored as well as ordinary tabs.
Updated•3 years ago
|
Comment 9•1 year ago
|
||
I managed to hit this in currently Nightly. Not exactly STR but:
a) After a restart (with correct tabs) the New Tab Page did not respond to clicks.
b) Closed the browser, restart.
c) Browser restarts only with the pinned tabs.
d) History->Recently Closed Windows restores all other tabs, but now in a separate window.
Comment 10•1 year ago
|
||
(In reply to Gian-Carlo Pascutto [:gcp] from comment #9)
I managed to hit this in currently Nightly. Not exactly STR but:
a) After a restart (with correct tabs) the New Tab Page did not respond to clicks.
b) Closed the browser, restart.
c) Browser restarts only with the pinned tabs.
d) History->Recently Closed Windows restores all other tabs, but now in a separate window.
Any errors in the browser console when this happens? Is the state of the session restore pref still correct if checked in the settings?
Comment 11•1 year ago
|
||
The pref is still correct (at least when I check now?).
I'll check the browser console next time it happens.
Comment 12•1 year ago
|
||
I had filed bug 1885010 for the issue that forced the restart. I guess if we have some error in how our "window" (waves hands vaguely) is set up, it could make sense that session restore gets similarly confused. (But don't ask me why pinned tabs are different from normal ones, somehow).
Comment 13•1 year ago
|
||
(In reply to Gian-Carlo Pascutto [:gcp] from comment #12)
I had filed bug 1885010 for the issue that forced the restart. I guess if we have some error in how our "window" (waves hands vaguely) is set up, it could make sense that session restore gets similarly confused. (But don't ask me why pinned tabs are different from normal ones, somehow).
Pinned tabs are restored even if autorestore is off. This has always worked this way.
Comment 14•1 year ago
|
||
I hit this bug like two times per week, still very reproducible in that sense.
Comment 15•7 months ago
|
||
I'm having similar issues on nightly where closing the macOS window with red close button results in the same outcome - after reopen only pinned tabs exist, the rest is gone. CMD+SHIFT+n brings back the old window with all tabs (but the pinned tabs are not present in that window).
CMD+SHIFT+t only brings back single tabs.
When quitting "normally" with CMD+q, all tabs are being reopened correctly.
Comment 16•7 months ago
|
||
(In reply to Yarik Kurmyza [:yarik] (he/him) (UTC+1) from comment #15)
I'm having similar issues on nightly where closing the macOS window with red close button results in the same outcome - after reopen only pinned tabs exist, the rest is gone. CMD+SHIFT+n brings back the old window with all tabs (but the pinned tabs are not present in that window).
CMD+SHIFT+t only brings back single tabs.When quitting "normally" with CMD+q, all tabs are being reopened correctly.
This is covered in bug 736974 and bug 750084.
Description
•