| 08:23 | <annevk> | MikeSmith: you might wanna look at the last couple of comments of https://bugzilla.mozilla.org/show_bug.cgi?id=1309358 |
| 08:23 | <annevk> | MikeSmith: a bunch of MDN regarding CORS got updated |
| 08:24 | <annevk> | (I saw Florian ping you in another bug as well, so you might have already seen it) |
| 15:34 | <annevk> | Domenic: you missed a non- in https://github.com/w3ctag/promises-guide/issues/60#issuecomment-519569673 |
| 16:21 | <Domenic> | annevk: I'm not seeing it... |
| 16:22 | <annevk> | Domenic: exceptional errors are the one thing you should use rejections for |
| 16:23 | <annevk> | Domenic: you meant non-exceptional errors |
| 16:24 | <Domenic> | annevk: ah right, thank you, my eyes just kept sliding right over it... |
| 20:10 | <Bakkot> | I observe that `new URL('http://a/%41').href` is 'http://a/A'; in Chrome and 'http://a/%41'; everywhere else, including Node. I am _pretty_ sure Chrome is wrong, but I'm having a little trouble following the URL parsing algorithm; does anyone know off the top of their head? |
| 20:15 | <annevk> | You are correct |
| 20:26 | <Bakkot> | thanks! |
| 20:46 | <dgrogan> | https://quirks.spec.whatwg.org/#the-percentage-height-calculation-quirk tries to find the containing block for resolving %height of an element. The last step is Jump to the first step. But there's nothing in the steps that changes _element_, making the steps an infinite loop. Am I missing something? |
| 21:57 | <jenny-m> | dgrogan: what about step 1? |
| 21:57 | <jenny-m> | "Let element be the nearest ancestor containing block of element, if there is one." |
| 21:58 | <dgrogan> | jenny-m: I do not know how I misread that. Thanks |