W3C home > Mailing lists > Public > public-webapi@w3.org > November 2005

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

From: Karl Pongratz <karlhp@karlhp.com>
Date: Tue, 22 Nov 2005 21:37:36 +0200
Message-ID: <43837380.3040600@karlhp.com>
To: Anne van Kesteren <annevk@opera.com>
CC: public-webapi@w3.org

Okay, it saves the DOM, that sounds better. Could that cause any memory 
problems? I.e. take 100 different document DOM states, each with a table 
of 500 rows and 10 columns. Or is the DOM state somewhere cached on disk 
anyway?

Anne van Kesteren wrote:

> On Tue, 22 Nov 2005 17:17:24 +0100, Karl Pongratz <karlhp@karlhp.com>  
> wrote:
>
>> How do I return to a document in the web browser history which has 
>> been  added via pushState()?
>
>
> Probably by pressing the back button.

>> It means what does pushState() save, does it save the entire DOM of 
>> a  document or does it just save some sort of event handler which is 
>> fired  when going Back/Forward.
>
>
> It saves the DOM.
>
> You can all read this in the draft:
>  <http://whatwg.org/specs/web-apps/current-work/#pushstate>
>
>
Received on Tuesday, 22 November 2005 19:38:14 GMT

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