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

[whatwg] Proposed changes to the History API

From: Mike Wilson <mikewse@hotmail.com>
Date: Fri, 21 Aug 2009 12:02:28 +0200
Message-ID: <BAY116-DAV10088A74A1A8D2E34BBF37A4FC0@phx.gbl>
Justin Lebar wrote:
> On Wed, Aug 19, 2009 at 5:31 PM, Jeremy Orlow wrote:
> > but here it seems like everything can just stay in memory...right?
> 
> My thought was that if you had a tab open and restarted the browser,
> that the state objects would be there after the restart, so we'd have
> to serialize to disk.  I also thought that we'd persist this state
> data even after we take a Document out of memory.

This part begs a couple more questions :-)

What you're essentially saying here is that when restarting
the browser, you will also restore history data, correct?

For tabs that were open when the browser was closed, this 
will mean that these will reappear after restart with full 
history, being able to go Back and restore state on
previous pages?

But for pages that were explicitly closed, and then 
navigated to in a "new" tab, will you restore the full
history in these as well? And is that really desired from
a user pov? (It seems you will be haunted by the same page
history forever, even if the corresponding server state
expired a long time ago.)

And if there has been several sessions in parallel on that
URL space, which one do you respawn for a navigation to a 
related page in a new tab?

Best regards
Mike
Received on Friday, 21 August 2009 03:02:28 UTC

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