Timothy Gu

Neither Blink nor Gecko allows multiple `NamedConstructor`s either.

For the second advice, would it suffice to say "When designing APIs that take a buffer as input"? For "output parameter" usage, I don't think there's a blanket advice we...

Another issue is static methods. At least with Chrome and Firefox and at least with `DOMRect`, static factory functions use the **current** realm for the newly created object: ```js //...

That's quite fair, and I would be satisfied if this is spec'd as such. However, newer ES primitives like `Array.from` and `Promise.all` use the **this** value to determine what to...

Here're my thoughts. Can this be a userland function instead? I can imagine people asking for other related functions, like say `DOMException.ignoreNotFound` meaning "only bubble up errors if they are...

Are there tests available for this?

All Web IDL methods are enumerable (e.g., `Headers.prototype.get`), which is different from ECMAScript (e.g., `Map.prototype.get`). What you see in iterators is just an extension of this difference. It’s too late...

Since Web IDL never seems to say an IDL ArrayBuffer has to be an actual JavaScript ArrayBuffer, couldn't you just use `ArrayBuffer` as the return type in IDL? I.e., the...

Or we can just enforce the relative order of members declared in the definition of an interface in a single IDL fragment, though that does cause questions like this: ```webidl...

@tobie Well, can't we leave inter-IDL fragment order undefined/implementation-defined? Like isn't relative order within the IDL fragment all we really care about in real life?