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: Mon, 21 Nov 2005 21:03:40 +0200
Message-ID: <43821A0C.6040408@karlhp.com>
To: Anne van Kesteren <annevk@opera.com>
CC: public-webapi@w3.org

There is yet the question if pushState() requires to execute JavaScript 
to display the altered document.

In case that the document DOM must me recreated by the developer it 
sounds similar to an onload event handler. If I remember correctly Eric 
Costello mentioned somewhere that such an approach causes timing 
problems. As more complex the DOM of a document as more problems it 
probably causes.

Does pushState() solve this problem?

Anne van Kesteren wrote:

> On Sun, 20 Nov 2005 10:37:05 +0100, Karl Pongratz <karlhp@karlhp.com>  
> wrote:
>> However, the WebForms and WebApplications draft specification goes 
>> far  beyond that and will probably require a huge effort to be 
>> implemented  compared to a single document.save() or similar function.
> Well, the extensions to the History object could be implemented  
> separately. There has been some talk on the WHATWG mailing list 
> already to  extend the pushState() method in such a way that it would 
> accept a second  argument, an identifier, but a clear proposal for 
> that that does not  interfer with security et cetera has not yet been 
> made.
> (And lots of what is in those drafts is actually specifying what 
> browsers  have implemented already. There are new features as  well, 
> but those are  mostly based on existing implementations et cetera.)
Received on Monday, 21 November 2005 19:04:37 UTC

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