| 15:10 | <eeeps> | annevk: guten tag/abend |
| 15:13 | <eeeps> | re: https://github.com/whatwg/html/pull/5112#discussion_r370637869... if I go with a step 22 right after the fetch, should I "still wait until the result of fetch is either an error or response?", and queue a task? Like, could the current language just be copy and pasted? |
| 15:14 | <eeeps> | (the other place that it seemed like it might make sense to do this was not asap but just in time - right before the image presentation was updated, after the UA could determine the width/height of the image) |
| 15:14 | <eeeps> | Good to know that headers are available asap though (and that there's a response object to work with...) |
| 15:16 | <eeeps> | And re: the larger question, about this only working for <img> - yep, that's an issue. Would you consider that a blocker or is it still useful to extend the <img> loading mechanics in ways that can be abstracted along with the rest of it? |
| 16:22 | <annevk> | eeeps: after the fetch there's a step that says "when the networking task source queues a task do x" you can do your thing during x |
| 16:23 | <annevk> | eeeps: it's a preexisting issue, but we should maybe make it more visible if we end up doing this, e.g., by having a bit fat issue marker that says this algorithm is to be abstracted and reused by various other places, such as background-image, etc. |
| 16:31 | <eeeps> | annevk: and I should still "Wait until the result of fetching is either a response or an error?" IIUC the response comes back, and is then populated by data incrementally, by the networking task source... |
| 16:32 | <eeeps> | "comes back" = is returned by Fetch |
| 16:32 | <annevk> | eeeps: the moment you get a task you have a response |
| 16:33 | <annevk> | eeeps: and that response will have all the headers as that's atomic |
| 16:33 | <annevk> | eeeps: the response body is not atomic however and will stream in |
| 16:33 | <annevk> | eeeps: does that help? |
| 16:35 | <eeeps> | That helps a lot, I think it clears up my core confusion. I'll move the logic and make a big fat issue marker. Thank you! |
| 17:20 | <annevk> | JakeA: https://twitter.com/jaffathecake/status/1220642131758518272 was very confusing to me |
| 17:20 | <annevk> | JakeA: I was like, you click the link, it goes there, all is well, no? |
| 17:20 | <annevk> | JakeA: anyway, TIL not everyone uses tab |
| 17:22 | <JakeA> | annevk: I'm not really a tabber. In general I think I use computers like a 90 year old man who find tin foil "a bit too advanced" |
| 17:23 | <JakeA> | I should force myself to learn more shortcuts |
| 17:24 | <annevk> | JakeA: making GitHub useful for mouse users by shitposting is worth it though |
| 17:24 | <annevk> | but yeah, shortcuts are nice and I should update my knowledge of them |
| 17:25 | annevk | learned cmd+spacebar recently... |
| 17:28 | <JakeA> | annevk: is that a GitHub thing? I think I have that as a global Alfred hotkey |
| 21:06 | <annevk> | JakeA: macOS |