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

A feature that requires a secure context will always be "denied" in
non-secure contexts. It would be possible to use this flag to throw an
exception from request() and possibly query(), but denying leads to one
fewer behavior that developers need to account for.

Preview at https://api.csswg.org/bikeshed/?url=https://raw.githubusercontent.com/jyasskin/permissions/secure-permissions/index.bs#requires-a-secure-context

@mikewest
You can view, comment on, or merge this pull request online at:

  https://github.com/w3c/permissions/pull/109

-- Commit Summary --

  * Allow features to 'require a secure context'.

-- File Changes --

    M index.bs (18)

-- Patch Links --

https://github.com/w3c/permissions/pull/109.patch
https://github.com/w3c/permissions/pull/109.diff

---
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

Received on Monday, 18 July 2016 22:35:17 UTC