Re: [w3c/permissions] WIP: Define a permission store (closes #384) (PR #390)

@johannhof commented on this pull request.



> +          </li>
+          <li>
+            Otherwise, [=list/append=] |newEntry| to the [=global permission store=].
+          </li>
+        </ol>
+        </p>
+        <p>
+        To <dfn class="export">remove a permission store entry</dfn> from the [=global permission store=] given a name, key and descriptor, run these steps:
+        <ol class="algorithm">
+          <li>
+          [=list/Remove=] the [=entry=] with the name |name|, key |key| and descriptor |descriptor| from the [=global permission store=].
+          </li>
+        </ol>
+        </p>
+        <p>
+        A <dfn class="export">permission store key</dfn> is a [=tuple=] of ([=origin=] top-level origin, [=origin=] embedded origin).

Regarding the extra implementation-defined field, do you reckon that's enough to give UAs flexibility to do what they want? I was thinking we could instead just define that UAs may maintain additional permission stores with implementation-defined scope and eviction rules.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/permissions/pull/390#discussion_r1026244734
You are receiving this because you are subscribed to this thread.

Message ID: <w3c/permissions/pull/390/review/1185814346@github.com>