Export to GitHub

scribefire - issue #714

Editor state should be saved when AutoSave and Save button are clicked


Posted on Aug 28, 2008 by Grumpy Kangaroo

The saved content is lost if the firefox crashed, even the user click the Save button before the firefox is crashed.

The problem is because every time when the ScribeFire starts, it will try to load the note from latest editor state. And after the editor load the 'old' note from state file, it will update/overwrite the saved newer notes.

So if the firefox crashed, ScribeFire will unfortunately lost the newer content but load old content stored in state file.

I have changed a few lines, which let ScribeFire 1. Save the editor state when AutoSave is triggered. 2. Save the editor state when the user click 'Save' button.

This is tested on 2.3.2 and Iceweasel (Firefox) 3.0.1 on Debian GNU/Linux sid.

Attachments

Comment #1

Posted on Aug 28, 2008 by Happy Elephant

(No comment was entered for this change.)

Comment #2

Posted on Sep 23, 2008 by Grumpy Kangaroo

It seems the newer 3.0.1 version still have this issue.

Comment #3

Posted on Oct 26, 2011 by Happy Elephant

This version of ScribeFire has been replaced by http://code.google.com/p/scribefire-chrome/

If this bug is still an issue for you in ScribeFire 4, please file a new report at http://code.google.com/p/scribefire-chrome/issues/entry

Status: Obsolete

Labels:
Type-Patch Priority-Medium