On Mon, Aug 28, 2006 at 08:11:45PM +0200, Steve Bennett wrote:
On 8/28/06, Jay R. Ashworth <jra(a)baylink.com>
wrote:
current
text is saved, the button grays out and changes to read
"Saved".
I don't like this. Browsers aren't smart enough for that. Hell, *apps*
aren't smart enough for that. When I say save, *save* damnit.
Fwiw, it works well. If you really desperately want to save again for
some paranoid reason, you can always add and remove a few spaces and
press 'save' then.
I've seen editors smart enough that whitespace that doesn't affect
formatting is ignored. I still don't like it.
Example:
MySpace: click "Log In" button. Button changes to "Logging In" and
greys out. Page submit times out (as it does all too frequently). Now
you can't re-click it, you have to reload the page first. Novice user
gets frustrated.
The only common reason given for this that's *almost* acceptable is "I
don't want them to submit their credit card sale twice... though the
*proper* answer for that one is "send a random cookie as a hidden field
on the form, pass it all the way to the SQL insert statement; if the
Unique trigger fires, complain."
* If you have a reply entered and try leaving the
page, it shows a
popup dialog asking if you want to discard changes (if not, it cancels
the page-leave, but doesn't save the draft, I think).
Yeah; I've seen that on-leave idea a couple of places. I like it quite
a bit, though permitting a browser to do it can have.. consequences.
It works well here.
Oh; I'm just saying that leaving that feature on in your browser can
enable... Bad Guys.
Cheers,
-- jra
--
Jay R. Ashworth jra(a)baylink.com
Designer Baylink RFC 2100
Ashworth & Associates The Things I Think '87 e24
St Petersburg FL USA
http://baylink.pitas.com +1 727 647 1274
The Internet: We paved paradise, and put up a snarking lot.