Re: [w3c/manifest] Privacy Review: handle start_url tracking (#399)

Safari's implementation results in the following scenario that I wrote about above:

> let's say you use a web app for a while in the browser, and then you install it. After installation, the web app loses all of its existing local state, including cookies, local storage, service workers, offline cache, etc.
>  * there's no sensible way to migrate everything to the new storage unless you copy the entire ETLD+1's cookies and the whole origin's worth of data, which may include way more than the web app actually owns.

As @benfrancis noted:

> If every application context has its own data jar, both of the above serve to fragment local storage across multiple jars. This has the side effect that the user is repeatedly forced to re-authenticate to access the same content in different contexts for example.

If you want to avoid the fragmentation and need for reauthentication (i.e. use the browser's storage for off-origin navigation), you then run into the navigation context switch change problems.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/manifest/issues/399#issuecomment-635093687