RESOLVED INVALID Bug 52568
WebKit/Safari losts all your editing without warning if an automatic refresh occurs while in the edition
https://bugs.webkit.org/show_bug.cgi?id=52568
Summary WebKit/Safari losts all your editing without warning if an automatic refresh ...
Juan Falgueras
Reported 2011-01-17 04:42:07 PST
WebKit/Safari losts all your editing without warning if an automatic refresh occurs while in the edition. While you are editing, a lock should avoid automatic refreshes of the page or, in other way, warns you before doing so. While in other circumstances it makes you feel confidence in preserving all you have done, because it warns you when, for example, you jump to another page having some unsent editing, when you are editing a long Edit Text and, precisely, lasts longer than the stablished automatic time for refreshing, you suddenly lost all your lost without a hitch.
Attachments
Alexey Proskuryakov
Comment 1 2011-01-17 10:26:22 PST
Do you have an example page where this happens? There are many ways to perform automatic refresh. But if I understand the bug correctly, it sounds more like a page design mistake, not something to improve browser side.
Juan Falgueras
Comment 2 2011-01-17 13:32:29 PST
But it's Safari, not the page-designer, who knows when the page has been edited (has text written inside the text boxes) and wants to be refreshes… isn't it?
Ryosuke Niwa
Comment 3 2011-02-17 03:05:02 PST
I think this bug is about preserving edited content when user presses refreshes the page or page refreshes using meta element or window.refresh(). I'm not sure if such a feature is even feasible given how rich text editing is implemented today. Ojan & Julie, do you have any comments on this feature request?
Levi Weintraub
Comment 4 2011-02-17 11:13:09 PST
(In reply to comment #2) > But it's Safari, not the page-designer, who knows when the page has been edited (has text written inside the text boxes) and wants to be refreshes… isn't it? The page designer has the ability to track changes to text boxes FWIW.
Ojan Vafai
Comment 5 2011-02-22 00:11:15 PST
I don't see how to work on this without a page where this happens. What's the site where this break? I'm marking as resolved for now. Feel free to reopen the bug if you add more information on how to reproduce the problem.
Note You need to log in before you can comment on or make changes to this bug.