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

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

From: Anne van Kesteren <annevk@opera.com>
Date: Tue, 22 Nov 2005 16:55:19 +0100
To: "Karl Pongratz" <karlhp@karlhp.com>
Cc: public-webapi@w3.org
Message-ID: <op.s0nfuhqc64w2qv@id-c0020.q42.local>


On Mon, 21 Nov 2005 20:03:40 +0100, Karl Pongratz <karlhp@karlhp.com>  
wrote:
> There is yet the question if pushState() requires to execute JavaScript  
> to display the altered document.

I'm not sure I understand. Could you elaborate?


-- 
Anne van Kesteren
<http://annevankesteren.nl/>
<http://www.opera.com/>

Received on Tuesday, 22 November 2005 15:57:20 GMT

This message: [ Message body ]
Next message: Sylvain Hellegouarch: "Re: Ajax Back/Forward History problem document state by document.save()"
Previous message: kenny heaton: "Re: Ajax Back/Forward History problem document state by document.save()"
In reply to: Karl Pongratz: "Re: Ajax Back/Forward History problem – saving document state by document.save()"
Next in thread: Karl Pongratz: "Re: Ajax Back/Forward History problem – saving document state by document.save()"
Reply: Karl Pongratz: "Re: Ajax Back/Forward History problem – saving document state by document.save()"
Reply: Jim Ley: "Re: Ajax Back/Forward History problem – saving document state by document.save()"

Mail actions: [ respond to this message ] [ mail a new topic ]
Contemporary messages sorted: [ by date ] [ by thread ] [ by subject ] [ by author ]
Help: [ How to use the archives ] [ Search in the archives ]

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