Closed Bug 373018 Opened 18 years ago Closed 18 years ago

restore session overwrites google docs collabaration to previous version (losing lots of work :'(

Categories

(Firefox :: Session Restore, defect)

x86
Linux
defect
Not set
critical

Tracking

()

VERIFIED INCOMPLETE

People

(Reporter: m_a_r_k, Unassigned)

Details

(Keywords: dataloss)

User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.2) Gecko/20060601 Firefox/2.0.0.2 (Ubuntu-edgy) Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.2) Gecko/20060601 Firefox/2.0.0.2 (Ubuntu-edgy) A uni friend ran firefox and chose to restore session. We are collaborating on document using google docs. It seemed restoring firefox in this way, opening said google docs document, reset the document to yesterdays state. Reproducible: Didn't try Steps to Reproduce: 1. 2. 3.
Severity: normal → critical
Keywords: dataloss
Not sure what Google Docs does with their URLs, POSTDATA, etc., but this sounds rather like an unfortunate interaction of the re-loading of some content having the side effect of making modifications in not that careful a webapp (don't they have a revision history / version undo feature?). Not sure what we could do differently here though - especially since without steps to reproduce we don't really know what the actual issue is. Would you mind investigating some more? What would be most helpful is a copy of the file sessionstore.bak in your profile right after restoring a crashed session reverted another (otherwise unimportant!) document.
I found later that there is a revision history feature as you say. As such, i guess it's really not such a problem although maybe still not completely ideal. Will try and replicate behaviour shortly but revising for exams atm.
Closing this bug as INCOMPLETE. Please reopen when/if you have steps to reproduce the issue from comment #0.
Status: UNCONFIRMED → RESOLVED
Closed: 18 years ago
Resolution: --- → INCOMPLETE
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.