| 00:24 | <tobie> | Domenic: dropping the passphrase helps. :D |
| 11:44 | <MikeSmith> | for the fetch API is there an equivalent of the XHR responseURL property? |
| 11:45 | <MikeSmith> | specifically, if a request gets redirected to a different URL does the fetch API expose the new URL in some (as XHR does with the responseURL property)? |
| 11:47 | <MikeSmith> | hmm is that was Response.url is? |
| 11:47 | <MikeSmith> | “A response has an associated url. It is a pointer to the last response URL in response’s url list and null if response’s url list is the empty list. |
| 11:48 | <MikeSmith> | so yeah I guess that is it |
| 11:48 | <MikeSmith> | given that URLs for redirects get added to the url list for the response |
| 12:09 | <annevk> | MikeSmith: yup |
| 12:26 | <MikeSmith> | annevk: thanks yeah I sometimes still get stuck in oldthink and forget that the fetch API makes all this stuff a lot easier and more intuitive |
| 12:27 | <annevk> | MikeSmith: fetch is dubleplusgood |
| 16:55 | <KevinMarks_> | Except that you can't get the intermediate urls |
| 19:22 | <annevk> | Can only offer that through opt-in |
| 20:00 | <iliakan> | what's the principal difference between dom.spec and html.spec? |
| 20:00 | <iliakan> | I see there's a lot of DOM stuff in html.spec.whatwg.org |
| 20:02 | <annevk> | iliakan: they are intertwined |
| 20:02 | <iliakan> | yeah, but what's the idea of difference? |
| 20:02 | <annevk> | iliakan: DOM is lower-level when it comes to node tree fundamentals |
| 20:02 | <iliakan> | ummm |
| 20:03 | <annevk> | iliakan: DOM defines node trees and events, HTML builds on that? |
| 20:09 | <iliakan> | so DOM is only basics about tree and manipulation? |
| 20:10 | <iliakan> | and Events |
| 20:24 | <annevk> | iliakan: pretty much |
| 21:16 | <iliakan> | is DOM spec intended for browsers only? |
| 21:16 | <iliakan> | or for any DOM parsers, server-based etc |
| 21:21 | <iliakan> | https://www.w3.org/TR/cssom-1/ (CSS objects) are not developed by WhatWG? |