- From: Boris Zbarsky <notifications@github.com>
- Date: Tue, 10 May 2016 13:15:44 -0700
- To: heycam/webidl <webidl@noreply.github.com>
- Cc:
- Message-ID: <heycam/webidl/issues/119/218277537@github.com>
It's both. > Does it mean that [SecureContext] implies [NoInterfaceObject] in non-Secure Contexts? The relevant normative text is http://heycam.github.io/webidl/#dfn-exposed (which explicitly references the "available only in secure contexts" state) and http://heycam.github.io/webidl/#es-interfaces which says that things that are not "exposed" in the `#dfn-exposed` sense do not generate properties on the global. > Or does it mean that all of an interface's members are only exposed within a secure context? The normative text here is http://heycam.github.io/webidl/#SecureContext where it says that for an interface member that doesn't have `[SecureContext]` specified explicitly: > The interface member is available only in secure contexts if and only if the interface or partial interface the member is declared on is. and then back to `#dfn-exposed` referencing this state and the existing infrastructure using `#dfn-exposed` to control existence of properties for interface members. --- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/heycam/webidl/issues/119#issuecomment-218277537
Received on Tuesday, 10 May 2016 20:18:30 UTC