Re: [permissions] Let each permission refine its algorithms and store data. (#66)

> +          A <dfn data-export="">permission request algorithm</dfn>
> +        </dt>
> +        <dd>
> +          Takes the previously-stored <a>permission storage type</a>, an
> +          <a>associated PermissionDescriptor</a>, and a newly-created
> +          <a>permission result type</a>, shows the user any necessary prompt to
> +          try to increase permissions, and updates the <a>permission storage
> +          type</a> and <a>permission result type</a> to match. Used by <a for=
> +          "Permissions" lt="request">Permissions.request()</a>, which handles
> +          reading and writing the <a>permission store</a>.
> +        </dd>
> +        <dt>
> +          A <dfn data-export="">permission revocation algorithm</dfn>
> +        </dt>
> +        <dd>
> +          After <a for="Permissions" lt="revoke">Permissions.revoke()</a>

This paragraph is inconsistent with the other two algorithms. Should be something like "Takes no arguments. Updates any other parts of the implementation that need to be kept in sync after an entry is removed from the permission store. Triggered by Permissions's revoke() method.

---
Reply to this email directly or view it on GitHub:
https://github.com/w3c/permissions/pull/66/files#r55889814