Re: [whatwg/storage] Integrate with the Permissions spec. (#36)

>  
>  <p class="note">When granted to an <a>origin</a>, the persistence permission can be used to protect
>  storage from the user agent's clearing policies. The user agent cannot clear storage marked as
>  persistent without involvement from the <a>origin</a> or user. This makes it particularly useful for
>  resources the user needs to have available while offline or resources the user creates locally.
>  
> -<p class="XXX">We will eventually integrate with the Permissions API, with the identifier
> -"<dfn export for=PermissionName type=enum-value><code>persistent-storage</code></dfn>", but since
> -that specification is not in great shape at the moment that has not happened yet.
> +The <dfn for="PermissionName" enum-value>"<code>persistent-storage</code>"</dfn> <a>powerful feature</a>'s
> +permission-related flags, algorithms, and types are defaulted except for:
> +
> +<dl>
> +  <dt><a>permission state</a></dt>
> +  <dd>
> +    <code>{name: {{"persistent-storage"}}}</code>'s <a>permission state</a> must
> +    have the same value for all <a>environment settings objects</a> with a given <a>origin</a>.
> +  </dd>

The wrapping here is not correct. Basically since `<dd>` doesn't have multiple block children everything needs to be on the same line with it, and then subject to 100 col wrapping. It might also make sense to use a `<p>` inside the `<dd>` (and below) since in the future the algorithm below might get more complicated. Adding the `<p>` would not change the wrapping rules since it's the only block child at that point.

---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/storage/pull/36/files/a5e9e69063941f9cc7f50a1a10d57f5b5ab7de52#r72428915