| 06:41 | <annevk> | The Freelancer: namedItem() is not the problem, but the corresponding getter (Web IDL, special operation) is. That allows for easy confusion between elements of the collection and members of the collection object instance due to the way JavaScript works. |
| 08:05 | <The Freelancer> | annevk: I didn't understand what you said. If you don't mind, can you please elaborate it a bit further.... |
| 10:15 | <annevk> | The Freelancer: say you have an element whose ID is length that is part of collection; what does collection["length"] return? |
| 11:20 | <The Freelancer> | Ok, great. Now, I get that. |
| 11:21 | <The Freelancer> | annevk: So HTMLCollection doesn't have this problem, right? |
| 14:02 | <nicolo-ribaudo> | Hello! I'm reading the whatwg/html spec, and I'm confused by the difference between the running script and the active script. Is it possible that they are always the same thing? |
| 18:52 | <jschoi> | nicolo-ribaudo: When the topmost element of the execution context stack (i.e., the running execution context) has a null ScriptOrModule component (e.g., it is the context created by InitializeHostDefinedRealm), then GetActiveScriptOrModule will not return the running execution context, right? |
| 20:02 | <nicolo-ribaudo> | nicolo-ribaudo: When the topmost element of the execution context stack (i.e., the running execution context) has a null ScriptOrModule component (e.g., it is the context created by InitializeHostDefinedRealm), then GetActiveScriptOrModule will not return the running execution context, right? |