| 06:03 | <MikeSmith> | annevk: Domenic is there some github issues that was the context for the CORS discussion? |
| 07:39 | <MikeSmith> | annevk: “document family” seems like the wrong/misleading term for what it’s defining it |
| 07:40 | <MikeSmith> | seems like that wrong analogy |
| 07:40 | <MikeSmith> | but I guess I can’t think of a better one |
| 10:27 | <annevk> | Yeah dunno either, it'll probably go away whenever someone rewrites history... |
| 12:40 | <zcorpan_> | annevk: re https://github.com/web-platform-tests/wpt/pull/15669 , for <iframe onload=w(1) src="http://ghjkghj">;, chrome fires load but safari and firefox don't |
| 12:43 | <annevk> | zcorpan_: ah, I tried http://test:test/ and there they all did load |
| 12:44 | <annevk> | zcorpan_: network errors are hard :/ |
| 12:44 | <annevk> | (also the spec sucks) |
| 12:44 | <zcorpan_> | that's a URL parse error right? |
| 12:44 | <annevk> | yeah |
| 12:45 | <annevk> | and yeah, I realized that too |
| 12:46 | <zcorpan_> | yep. looks like that navigates to about:blank per spec https://html.spec.whatwg.org/multipage/iframe-embed-object.html#otherwise-steps-for-iframe-or-frame-elements |
| 12:49 | <zcorpan_> | https://html.spec.whatwg.org/multipage/browsing-the-web.html#process-a-navigate-response step 1 doesn't say to fire load, so chrome has a bug |
| 12:55 | <zcorpan_> | https://bugs.chromium.org/p/chromium/issues/detail?id=938279 |
| 12:57 | <zcorpan_> | as for contentDocument http://software.hixie.ch/utilities/js/live-dom-viewer/saved/6736 |
| 13:01 | <zcorpan_> | but also http://software.hixie.ch/utilities/js/live-dom-viewer/saved/6737 |
| 13:05 | <annevk> | zcorpan_: 6736 reads contentDocument too quickly |
| 13:06 | <zcorpan_> | ah yes |
| 16:38 | <Domenic> | Are there cases where .parentElement !== null and .parentElement !== .parentNode |
| 16:50 | <Domenic> | littledan: in case it's quick to answer, does your modules PR handle cases like `module "std:x" { interface Node { }; interface Foo { void op(Node n); } }`? In particular how do we know which `Node` `op()` takes, the global one or the module-local one? |
| 16:50 | <Domenic> | If it's not quick to answer I'll ask on the issue tracker. |
| 16:51 | <littledan> | Domenic, That's a good question. It doesn't have any text about that |
| 16:51 | <Domenic> | Cool, will raise it on the tracker for discussion. |
| 17:05 | <annevk> | Domenic: I thought parentElement returned parentNode if an Element and null otherwise |
| 17:05 | <Domenic> | I think you are right |
| 17:06 | <Domenic> | I just got turned around |
| 17:06 | <Domenic> | So in that case I declare parentElement a "slightly bad part" of DOM. |
| 17:06 | <annevk> | heh |