Closed
Bug 351093
Opened 19 years ago
Closed 19 years ago
Implement Firefox's undo close tab feature in SeaMonkey (previously "Closing last tab causes data loss - browsing history not kept.")
Categories
(SeaMonkey :: UI Design, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 350416
People
(Reporter: jasonb, Assigned: csthomas)
Details
(Keywords: dataloss)
With the fix for bug 156082, closing the last tab now loads a blank page. However, in doing this, all browsing history is lost. If you accidentally close the last tab, you can't click on Back to bring up the page you were just viewing. This could be a big problem. (Previously, the page didn't go away.)
If we're going to go to a blank page, we should at least keep browser history so that Back can be used to recover from accidental closure.
Over to Chris, at least for now, for his thoughts.
| Assignee | ||
Comment 1•19 years ago
|
||
This is by design. Closing the other n-1 tabs blew away their history, so the same thing should happen for the last tab.
For what it's worth, when bug 350416 is fixed (and it's something I'm hoping to have in time for 1.1b), closing tabs will no longer be serious dataloss.
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → INVALID
| Reporter | ||
Comment 2•19 years ago
|
||
Okay. If we're going to treat the last tab exactly the same as the other tabs, then reopening this to turn it into a SeaMonkey specific request for Firefox's (bug 254021) undo close tab functionality, just as it's also been requested for Camino (bug 316458).
Status: RESOLVED → REOPENED
Resolution: INVALID → ---
Summary: Closing last tab causes data loss - browsing history not kept. → Implement Firefox's undo close tab feature in SeaMonkey (previously "Closing last tab causes data loss - browsing history not kept.")
| Reporter | ||
Comment 3•19 years ago
|
||
Doh! I'm stupid. I didn't fully read Chris' comments. INVALID is still the wrong resolution.
*** This bug has been marked as a duplicate of 350416 ***
Status: REOPENED → RESOLVED
Closed: 19 years ago → 19 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•