Ms2ger

That's a fair point. Maybe we could use "is a `Text` object" for IDL values, and use "implements" for JS values? I think using "corresponding ECMAScript value" would generally be...

In the spec as written, it'll return a rejected promise and the success steps won't be run. Let's take a look at what APIs take a Promise argument anyway: -...

Fwiw, I'm pretty sure Gecko defines methods and attributes separately, so we'd have to look at the relative order within those groups.

Gecko's implementation has been doing methods, then attributes (and then constants) since first using WebIDL in 2012 (; I don't think we cared about enumeration order at the time.

Probably not.

You're correct, I got confused. I think this is better.

@bzbarsky any more thoughts?

Good point, oversight on my side. PRd as #1137.

I rebased and updated to some name changes in the proposal - lemme know if this is blocked on anything on our side.

> Thanks @Ms2ger for taking this on. I think @domenic will have to review the module bits, which seems like the most substantive change as at least per [tc39/proposal-shadowrealm#225 (comment)](https://github.com/tc39/proposal-shadowrealm/issues/225#issuecomment-592159225)...