W3C home > Mailing lists > Public > public-webapi@w3.org > January 2006

Re: Ajax Back/Forward History problem - saving document state by document.save()

From: Anthony Ettinger <aettinger@sdsualumni.org>
Date: Mon, 9 Jan 2006 10:10:31 -0800
Message-ID: <3fc6b2fb0601091010j204f6b59l56f16220c2b0c38c@mail.gmail.com>
To: Vladimir Kelman <vlad@vkelman.com>
Cc: public-webapi@w3.org
On 1/9/06, Vladimir Kelman <vlad@vkelman.com> wrote:
>
>
> "providing to a page that can be in many states, enough information that
> it can recreate a previous state"
>
> Mark,
> yes it's a good goal, it's definitely better than trying to remember a
> state itself. But my point was basically that: you have to stop on some
> level. You cannot remember and make reproducible each state after tiny
> change. It's better to allow an opposite thing: to warn user how "hit a
> Back or Forward" button that system is going to leave current
> application completely and will not be able to re-enter a current
> "micro-state". To warn a user and give him ability to Cancel - just like
>   Internet Expolrer's onbeforeunload() event works.



My 2 cents. If you can undo past a save in some apps, you should be able to
do it on the web too.
Received on Monday, 9 January 2006 18:10:36 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:18:53 GMT