Re: [w3c/permissions] Should we SecureContext the API (#235)

I think that this API is an important part of allowing pages to reason about what features are and are not available; I don't see the harm in allowing pages to query, even if the answer is a guaranteed *no* every time. We're already removing the underlying features themselves; keeping this API means that developers don't need to write special HTTP-only code to determine that.

As an additional point, If we move to merge some of the permissions policy API into this API, then there will likely be more features that are usable in non-secure contexts. (Things like fullscreen, picture-in-picture, storage access). I think it would still make sense to be able to query those in any context where they are available.

-- 
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/issues/235#issuecomment-823465460