Re: [w3c/permissions] Allow UAs to maintain zero or multiple permission stores. (#95)

>      </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.

The rules for which subset of the permissions stores that the browser will actually write to are browser-specific, as we've established.  This algorithm doesn't really enable that.  It says "find all that match", then "write too all of them".  It needs to include a second step that is "identify which of the stores that the user agent wants to persist the change to".

---
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#r61534585