When creating a global object the realm is not yet initialized

[annevk]

What is the issue with the Web IDL Standard?

This hits step 1 of https://webidl.spec.whatwg.org/#internally-create-a-new-object-implementing-the-interface

But also 1.1 of https://webidl.spec.whatwg.org/#define-the-operations and 2.2.1 of https://webidl.spec.whatwg.org/#dfn-create-operation-function.

Some of this could maybe be helped if we set realm.[[GlobalObject]] ourselves, but there's a further issue in that https://webidl.spec.whatwg.org/#dfn-exposed needs access to the settings object which isn't created until after the realm in HTML. I think that's information we need to pass in explicitly somehow instead, at least when allocating the global object.

[jmdyck]

To be clear, the realm is not completely initialized. It does have realm.[[Intrinsics]], which is useful.

Some of this could maybe be helped if we set realm.[[GlobalObject]] ourselves,

Set it to what? A really simple object, or a special value like null?

[annevk]

I was thinking after step 6 of https://webidl.spec.whatwg.org/#internally-create-a-new-object-implementing-the-interface (in the case where we are creating a global object). That would at least do the right thing for 2.2.1 of https://webidl.spec.whatwg.org/#dfn-create-operation-function (and a similar step for getters and setters).

I think that leaves solving for "exposed". Perhaps that's a check we can bypass when we create the global.

[jmdyck]

Ah, you mean set realm.[[GlobalObject]] to its proper value, just earlier in the whole process than happens currently.