- From: Jeffrey Yasskin <notifications@github.com>
- Date: Fri, 29 Apr 2016 08:06:47 -0700
- To: w3c/permissions <permissions@noreply.github.com>
- Cc:
Received on Friday, 29 April 2016 15:07:27 UTC
> </li> > - <li>Otherwise, it MUST write the new {{PermissionStorage}} to its > - permission store. > + <li> > + Write a mapping from <var>name</var> to <var>storage</var> into each > + <a>permission store</a> in <var>stores</var>, overwriting any existing > + mapping with the same <var>name</var>. > + > + Issue(91): This isn't quite sufficient for complex {{PermissionStorage}} > + subclasses, which may need to modify the old storage instead of just > + overwriting it. Oh, I meant "Let stores be a collection of zero or more permission stores associated with the same origin as settings." to allow the UA to pick whichever subset it wants, possibly differently for each operation. --- 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/permissions/pull/95/files/9a98a3cc8c47bc4aba961d8bf7244bb1b57f1f72#r61592212
Received on Friday, 29 April 2016 15:07:27 UTC