Re: [w3c/permissions] Allow features to 'require a secure context'. (#109)

>    </p>
>    <dl>
> +    <dt>A <dfn export>requires a secure context</dfn> flag</dt>
> +    <dd>
> +      Indicates that the feature will always be {{"denied"}} in <a>non-secure
> +      contexts</a>. This flag defaults to un-set.

Arguably, we should default this to "set", and make features explicitly say that they don't require a secure context... Then I'd probably reword it to reverse the sense: "allowed in non-secure contexts" defaulting again to un-set.

Thoughts?

---
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/109/files/9473be46d911c010a9f5e14e8626adbfb4690d04#r71244165