[whatwg] Proposed changes to the History API

[Justin Lebar]

On Wed, Aug 19, 2009 at 5:31 PM, Jeremy Orlow<jorlow at chromium.org> 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.

It might be possible to store some subset of DOM objects while still
meeting those requirements, but that seems like it might be a serious
can of worms.  Do you have a use case which would be facilitated by
being able to store some DOM objects in this way?

-Justin