| 06:52 | <annevk> | littledan: if you do something like realmGlobal.document = new FakeDocument();, wouldn't that FakeDocument have the wrong global associated with it? |
| 07:08 | annevk | filed https://github.com/tc39/proposal-realms/issues/268 |
| 10:17 | <littledan> | Thanks for the ping annevk , following up on the issue. I am not sure if I understand the concern. |
| 17:27 | <annevk> | Domenic: so does HTML dispatch a load event for network errors for <iframe>? I thought it didn't define that yet |
| 17:28 | <Domenic> | annevk: yeah it does, I remember when I wrote tests for <embed> I looked it up and it already does for <iframe>... lemme find it |
| 17:28 | <annevk> | (otherwise, why would 125 be open) |
| 17:28 | <Domenic> | > iframe is already specified to fire a load event when any document is created, including a network error document (created via https://html.spec.whatwg.org/#read-ua-inline) |
| 17:28 | <Domenic> | https://github.com/whatwg/html/pull/4247#issuecomment-657715522 |
| 17:29 | <Domenic> | annevk: well, I figured 125 was open because it's useful to know the difference between loads and errors |
| 17:29 | <Domenic> | So https://github.com/whatwg/html/issues/125#issuecomment-561164029 I guess |
| 17:31 | <annevk> | I see, I guess some other tests need updating then and I should make more of an effort to get Firefox to align |
| 17:33 | <annevk> | Oh wow "When a Document in an iframe is marked as completely loaded, the user agent must run the iframe load event steps." that's some action-at-a-distance |
| 17:39 | <Domenic> | Hmm yeah... looks like 10-15 references to "completely loaded".... I bet we could just make those into normal function calls. |
| 17:39 | <Domenic> | Seems like we need to keep the boolean |
| 17:39 | <Domenic> | I'll open a tracking issue for that |