| 01:29 | <SamB> | ... strange ... https://dom.spec.whatwg.org/service-worker.js is seeing fetch requests for 'chrome-extension://' URLs. |
| 03:11 | <SamB> | and double WTH, Chrome does DNS resolution while *parsing* chrome-extension:// URLs ??? |
| 03:12 | <SamB> | okay maybe not |
| 03:12 | <SamB> | chrome-extension://404/ gets treated oddly |
| 23:28 | <MikeSmith> | annevk: is the following actually correct? |
| 23:28 | <MikeSmith> | https://html.spec.whatwg.org/multipage/origin.html#concept-origin-tuple |
| 23:28 | <MikeSmith> | A tuple origin |
| 23:28 | <MikeSmith> | A tuple consists of: |
| 23:28 | <MikeSmith> | A scheme (a scheme). |
| 23:28 | <MikeSmith> | A host (a host). |
| 23:28 | <MikeSmith> | A port (a port). |
| 23:28 | <MikeSmith> | A domain (null or a domain). Null unless stated otherwise. |
| 23:29 | <MikeSmith> | .. |
| 23:29 | <MikeSmith> | a tuple consisting of four parts? |
| 23:30 | <MikeSmith> | why both “A host” and “A domain”? |
| 23:31 | <TimothyGu> | The link for "tuple" should go to https://infra.spec.whatwg.org/#tuple, but yes that's correct |
| 23:31 | <TimothyGu> | The reason why we have both is `document.domain` I believe |
| 23:31 | <TimothyGu> | See https://html.spec.whatwg.org/multipage/origin.html#relaxing-the-same-origin-restriction |
| 23:32 | <TimothyGu> | MikeSmith: ^^ |
| 23:32 | <MikeSmith> | TimothyGu: yup, much thanks — I just now followed the backrefs and it’s more clear |