Closed
Bug 1030645
Opened 10 years ago
Closed 8 years ago
Session restore does not save / restore some user-entered data
Categories
(Firefox :: Session Restore, defect)
Firefox
Session Restore
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: nicolas.barbulesco, Unassigned)
References
Details
(Keywords: dataloss)
Session restore usually saves and restore form data. However, some user-entered data are not saved neither restored. Example 1 : The user has written a comment in Disqus. Example 2 : The user is editing Wikipedia in WYSIWYG. In case of crash, or clean quit, the user expects to have these restored. Firefox does not restore these. This is data loss. These use "contenteditable". It would be nice that Firefox save and restore "contenteditable" user-entered data. Firefox should save the "contenteditable" content only if it has been modified by the user - otherwise the session store would become huge. Thank you. Nicolas
Comment 1•10 years ago
|
||
I cannot reproduce. Here's what I did: * edit the following page: https://commons.wikimedia.org/w/index.php?title=Commons:Sandbox&action=edit * write a few words * quit and restart Firefox The few words were restored.
Reporter | ||
Comment 2•10 years ago
|
||
(In reply to David Rajchenbach Teller [:Yoric] from comment #1) > I cannot reproduce. > > Here's what I did: > * edit the following page: > https://commons.wikimedia.org/w/index.php?title=Commons:Sandbox&action=edit > * write a few words > * quit and restart Firefox > > The few words were restored. Dave, that is normal, you used the (good old) wikicode editor. I was speaking of Wikipedia's WYSIWYG editor. You may try it here : https://en.wikipedia.org/wiki/User:Sandbox?veaction=edit
Comment 3•9 years ago
|
||
Nicolas, do you still see this issue?
Flags: needinfo?(nicolas.barbulesco)
Keywords: dataloss
Comment 4•8 years ago
|
||
Haven't heard from the reporter in a long time, closing incomplete.
Status: UNCONFIRMED → RESOLVED
Closed: 8 years ago
Flags: needinfo?(nicolas.barbulesco)
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•