Justin Lebar wrote: > Maybe the right solution is to have a pageStorage object, which works > just like sessionStorage but is local to a session history entry and > perhaps carries some weak promise of persistence.
Yes, I was also thinking that being able to store key/value pairs, instead of a single state object, would be good. It would be nice to see the same kind of API be reused throughout the different state/storage mechanisms. Best regards Mike
