Re: [webidl] Add a [SecureContext] operator attribute (#65)

> It seems IE behave like that.

Not sure what you mean, we setup all APIs at script engine creation time.

As far as throw vs. change exposure; throw works for me. I was under the impression that `document.domain` could not change a document's secure context state. Did I understand the following to mean that it can't today, but that you [Mike] want to enable such a feature?

> I want to support that feature. To that end, I'd prefer throwing, as outlined in this PR.

Because I very much understand the desire to reduce the "I'm not allowed to use an API because its in a secure context" problem down to a simple API feature-detect. The counter-argument is that you already provide a feature detect via `isSecureContext`. :) So, I'm not passionate about it either way.

---
Reply to this email directly or view it on GitHub:
https://github.com/heycam/webidl/pull/65#issuecomment-156497032