Re: [heycam/webidl] Add namespaces (#121)

> +
> +          <p>
> +            The order that members appear has significance both for <a
> +            href='#idl-overloading'>overloading</a> and for property enumeration in the <a
> +            href='#es-namespaces'>ECMAScript binding</a>.
> +          </p>
> +
> +          <p>
> +            Note that unlike interfaces or dictionaries, namespaces do not create types.
> +          </p>
> +
> +          <p>
> +            Only the <a class='xattr' href='#Exposed'>[Exposed]</a> and <a class='xattr'
> +            href='#SecureContext'>[SecureContext]</a> extended attributes are applicable to
> +            namespaces. When declaring a <a class='dfnref' href='#dfn-partial-namespace'>partial
> +            namespace</a>, the partial namespace must have the same extended attributes (and

Why?  This seems like an overly onerous requirement to me.  In particular, why would we prohibit this:

    [Exposed=(Window,Worker)]
    namespace foo {
      void func1();
    };
    [Exposed=Worker]
    partial namespace foo {
      void func2();
    };

as a mechanism for extending a namespace with some members that have more restricted exposure?  Similar for [SecureContext].  I don't see a reason to make these extended attributes work differently from the way they work for interfaces, if we're going to support partial namespaces at all.

-- 
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/121/files/23ba5276699574269bd955c67d60bd6ce586337f#r76247465