Open Bug 434232 Opened 17 years ago Updated 3 years ago

track URLs that were opened but never closed explicitly

Categories

(Firefox :: Session Restore, enhancement)

x86
Windows XP
enhancement

Tracking

()

People

(Reporter: yurkennis, Unassigned)

References

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9) Gecko/2008051206 Firefox/3.0 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9) Firefox/3.0 beta 5 I have a feature request to keep track in History(?) of URLs that were opened by a user, but he never explicitly closed manually/via page's javascript. My reason behind this is: - I several time lost parts of my open tab sessions, and it is nearly impossible to restore a dozen of windows with a dozen of open tabs in each when many of them were opened months ago "to be read later" - if it may help, the last time I encountered such loss was when I got FF hang up opening some newly opened page, and restarts with/without Safe mode did not help. Then I turned back and forth between FF2.0 and FF3.0b5 for several times, until I found that half of my windows in restored session appear with tabs that all became blank, without any URLs in them. And from that point I tried to restore them manually--and never succeed in a reasonable time. My usage pattern is that each URL I open is some sort of ToDo for me, and when I lose half of my ToDo items, it doesn't make me happy. Reproducible: Didn't try
Severity: normal → enhancement
Status: UNCONFIRMED → NEW
Ever confirmed: true
After I experienced another major crash resulting in lost of URLs for ~100 open tabs, I created the following workaround. I scheduled a backup of a single file, which saves N last versions of it (N=100 to be sure :-) The only file I backup is this: C:\Documents and Settings\(my_login)\Application Data\Mozilla\Firefox\Profiles\i0mp360s.default\sessionstore.js A simple experiment seems to demonstrate that it works, but I will report later as I have a real data loss incident.
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.