Re: [heycam/webidl] Make [Exposed] mandatory, remove [PrimaryGlobal] (#423)

It seems ok to me.  Forcing all interfaces to always have extended attributes is a bit weird (leading to the question of why that required bit is not using dedicated syntax), but the general idea does have the benefit of forcing people to think about where their new API should be available.

Mixins are complicated.  Right now, the spec requires that the exposure set of a mixin be a subset of the exposure set of an interface.  That's because the exposure set of the mixin is the default exposure set of all the things being mixed in, and it doesn't make much sense to expose members in places where the interface is not exposed.  So we may well want to continue requiring an exposure set for mixins; if not, we need to figure out how things should actually behave.  In the proposal where mixins are not required to have [Exposed], what is the exposure set of their members, exactly?

For the same reason, we should probably require [Exposed] even for [NoInterfaceObject], again because it affects exposure of the 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/pull/423#issuecomment-326324329