W3C home > Mailing lists > Public > whatwg@whatwg.org > August 2009

[whatwg] HTML5 History Management

From: Mike Wilson <mikewse@hotmail.com>
Date: Wed, 5 Aug 2009 10:58:07 +0200
Message-ID: <BAY116-DAV2A7FC5D03F23E44C515C3A40D0@phx.gbl>
Nathan Hammond wrote:
> I should have stated this one with a goal: the ability
> to ensure that the popstate event always fires with a 
> full understanding of the (app/page) state when 
> navigating through history. This would be lost when a  
> user manually changes the hash. [...]
> Any other techniques for remembering data other than this 
> would still be a hack because, in and of itself, the data 
> stored are not uniquely tied to a particular history 
> state. [...]
> Using sessionStorage I have the additional task of mapping 
> the stored series of states to a particular visit of the 
> (app/page) if the user visits the site again after 
> navigating away: example.com -> whatwg.com -> example.com

Hi Nathan,

I think I touched on the same need in my thread "html5 
state handling: overview and extensions", see
http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2009-June/020423.html
or
http://www.nabble.com/html5-state-handling:-overview-and-extensions-td240347
73.html

See the table on "SCRIPT-CONTROLLED STATE" at the end of 
that mail. As you can see I am suggesting to add a state
construct for the missing Document state level. I'm just
back from vacation but I'm doing some more research and
hope to provide more information on that thread later 
this month.

Best regards
Mike Wilson
Received on Wednesday, 5 August 2009 01:58:07 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:59:15 UTC