Re: [w3c/permissions] Describe the permission store using constraints instead of a full model. (#96)

> -    <li>
> -      <var>name</var>
> -    </li>
> -    <li>
> -      <var>settings</var>' <a>origin</a>
> -    </li>
> -    <li>optional UA-specific data like whether <var>settings</var>'
> -    <a>browsing context</a> has a <a>parent browsing context</a>, or
> -    <var>settings</var>' <a>top-level browsing context</a>'s <a>origin</a>
> -    </li>
> -  </ol>
> +
> +  <p>
> +    The UA may store <a>permission entries</a> more persistently than a
> +    <a>realm</a>, but this specification doesn't constrain how.
> +  </p>

It should at least be constrained to origins. Cannot allow new kind of cookies. And ideally we do make it possible for certain permissions to require something more here. E.g., persistent storage isn't really useful without origin-wide permission.

---
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/96/files/6d6282b7405265cabec2c0ee30b69877d77d9dff#r63198276