- From: Anne van Kesteren <notifications@github.com>
- Date: Mon, 08 Aug 2016 00:53:50 -0700
- To: whatwg/storage <storage@noreply.github.com>
- Message-ID: <whatwg/storage/pull/36/r73834735@github.com>
> > <p class="note">When granted to an <a>origin</a>, the persistence permission can be used to protect > storage from the user agent's clearing policies. The user agent cannot clear storage marked as > persistent without involvement from the <a>origin</a> or user. This makes it particularly useful for > resources the user needs to have available while offline or resources the user creates locally. > > -<p class="XXX">We will eventually integrate with the Permissions API, with the identifier > -"<dfn export for=PermissionName type=enum-value><code>persistent-storage</code></dfn>", but since > -that specification is not in great shape at the moment that has not happened yet. > +The <dfn for="PermissionName" enum-value>"<code>persistent-storage</code>"</dfn> <a>powerful feature</a>'s > +permission-related flags, algorithms, and types are defaulted, except for: > + > +<dl> > + <dt><a>permission state</a></dt> > + <dd><code>{name: {{"persistent-storage"}}}</code>'s <a>permission state</a> must have the same > + value for all <a>environment settings objects</a> with a given <a>origin</a>.</dd> > I think the variety of existing stores is a good reason not to try to write up a single model that covers all of them. Isn't that what Permissions is? If Permissions is not that, what exactly is this integration supposed to be? --- 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/pull/36/files/52d4bac9ccc42d0307989cf262fbbb7094403340#r73834735
Received on Monday, 8 August 2016 19:24:46 UTC