05:47
<annevk>
The Freelancer: it does
09:50
<zcorpan>
The Freelancer: HTMLCollection has the problem but NodeList does not. The reason some browsers switched from NodeList to HTMLCollection anyway is for web compatibility. Some websites depended on collection.foobar working.
09:52
<zcorpan>
On a different note, I'll be off work between now and August 8 ☀️
10:36
<Luca Casonato>
With all the pre-requisites done now, I'd like to get https://github.com/whatwg/fetch/pull/1346 landed soon. annevk could you give it another review pass?
16:19
<jschoi>
nicolo-ribaudo: There are brief times when the running execution context is not null but its ScriptOrModule is null, right? For example, step 7 of https://tc39.es/ecma262/#sec-built-in-function-objects-call-thisargument-argumentslist.
16:19
<jschoi>
Also, hosts have leeway in what kind of execution contexts they are allowed to push onto the stack: https://tc39.es/ecma262/#sec-hostresolveimportedmodule
16:19
<jschoi>

An example of when referencingScriptOrModule can be null is in a web browser host. There, if a user clicks on a control given by <button type="button" onclick="import('./foo.mjs')">Click me</button> there will be no active script or module at the time the import() expression runs. More generally, this can happen in any situation where the host pushes execution contexts with null ScriptOrModule components onto the execution context stack.