- From: Tobie Langel <notifications@github.com>
- Date: Thu, 28 Sep 2017 16:00:50 +0000 (UTC)
- To: heycam/webidl <webidl@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Thursday, 28 September 2017 16:01:30 UTC
So in the #433, I'm voluntarily conservative with mixin's [exposure sets](https://s3.amazonaws.com/pr-preview/tobie/webidl/mixins.html#dfn-exposure-set). That is, mixin members inherit the host interface's "exposure set" unless they (or the mixin or partial mixin they're defined on) have an "own exposure set", in which case the mixin member's "exposure set" is the intersection of the two. It seems we should do the same for [SecureContext] . That is, if they're included in a host interface which is itself annotated with [SecureContext], then none of the mixin members should be exposed, regardless of whether or not the mixin itself, or any of its members has a [SecureContext] extended attribute. -- 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/118#issuecomment-332883204
Received on Thursday, 28 September 2017 16:01:30 UTC