Re: [whatwg/storage] Session storage and changing browsing contexts (#119)

I've been thinking about the event a bit more, and I don't think we need it. In fact, if "clone & swap" ends up being a stopgap before a shared model, we don't really want a bespoke event that might be useless in future.

There are a few ways for a page to become active 'later':

- Prerender
- Portals
- Bfcache

And in all cases, you need to look at session storage if you have state there. Firefox and Safari do not queue storage events for bfcached pages (Chrome's experimental implementation does, but is what what we want @altimin?).

Maybe the best rule for developers is to check session storage for changes after `'pageshow'`? For prerender, we can make sure the storage is swapped before that event.

The only sharp edge is that the `'pageshow'` event fires after `'load'` for some reason. We'd need to make sure there's an easy way to ignore the `'pageshow'` event for a page that wasn't 'hidden'.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/storage/issues/119#issuecomment-785771108