Re: Web IDL interfaces now require explicit [Exposed] annotations

On 10/1/19 11:39 AM, Eric Shepherd (Sheppy) wrote: Is the page “WebIDL bindings” up to date as well? That page describes gecko-specific aspects of IDL, so usually does not need to be updated for spec changes. That said, it looks like it was never updated for

Re: Web IDL interfaces now require explicit [Exposed] annotations

No. I didn't even know about that page ;-| Chris Mills MDN content lead & writers' team manager Mozilla Developer Network @chrisdavidmills On Tue, Oct 1, 2019 at 4:39 PM Eric Shepherd (Sheppy) wrote: > Is the page

Re: Web IDL interfaces now require explicit [Exposed] annotations

Is the page “WebIDL bindings” up to date as well? I often find it useful too. https://developer.mozilla.org/en-US/docs/Mozilla/WebIDL_bindings On October 1, 2019 at 5:58:36 AM, Christopher Mills (cmi...@mozilla.com) wrote: I've removed the mention of PrimaryGlobal from

Re: Web IDL interfaces now require explicit [Exposed] annotations

On 10/1/19 5:58 AM, Christopher Mills wrote: I've removed the mention of PrimaryGlobal from https://developer.mozilla.org/en-US/docs/MDN/Contribute/Howto/Write_an_API_reference/Information_contained_in_a_WebIDL_file. It was only a small mention. I also removed the separate mention of the

Re: Web IDL interfaces now require explicit [Exposed] annotations

I've removed the mention of PrimaryGlobal from https://developer.mozilla.org/en-US/docs/MDN/Contribute/Howto/Write_an_API_reference/Information_contained_in_a_WebIDL_file. It was only a small mention. I also removed the separate mention of the default value: "If no annotation is available, the

Web IDL interfaces now require explicit [Exposed] annotations

Starting today (on autoland,coming to m-c soon), there is no more [PrimaryGlobal] extended attribute on interfaces in our Web IDL, and therefore all interfaces need an explicit [Exposed] annotation saying where they are exposed (e.g. [Exposed=Window] for the case that used to not have any