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

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

From: Vladimir Kelman <vlad@vkelman.com>
Date: Mon, 09 Jan 2006 07:53:09 -0500
Message-ID: <43C25CB5.3000403@vkelman.com>
To: public-webapi@w3.org

"providing to a page that can be in many states, enough information that 
it can recreate a previous state"

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.

Vladimir Kelman
Received on Monday, 9 January 2006 12:53:26 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:16:19 UTC