Re: Scratchpad (Edit)/Personal Nodelet (add to scratchpad) : Lost update problem

Yes, you should have known better. A warning would probably be possible, and not all that difficult.. (I think, will check). However, automatically appending might not be the desired behaviour for some/most people (I usually prepend, for example). So one could warn at least, but what to do with the extra content? Assuming you have a decent browser, using the Back button and copying then might be possible..

Hmmm...

Comment on Re: Scratchpad (Edit)/Personal Nodelet (add to scratchpad) : Lost update problem

Replies are listed 'Best First'.
Re^2: Scratchpad (Edit)/Personal Nodelet (add to scratchpad) : Lost update problem by mhi (Friar) on Jun 29, 2004 at 16:09 UTC
Good point castaway! Here's what to do with the extra data when that happens: Simply show an edit screen with two forms: the current node content on top with a regular "submit" button and the rejected on the bottom with a "submit this instead" button or somesuch. That would make it very easy to eliminate the problem by cut-and-paste.	[reply]
Re^2: Scratchpad (Edit)/Personal Nodelet (add to scratchpad) : Lost update problem by ysth (Canon) on Jun 30, 2004 at 03:01 UTC
I'd lean toward just bailing out with a "Warning! Scratchpad has changed since editing began; return to display view or Submit again to override" if the update detects that the scratchpad was changed from how it was when the edit page was generated. Two ways to detect this: checksum or hidden field with the original content; which is better?	[reply]