| 03:03 | <domfarolino> | Domenic: So if the full response is not available at this point (https://github.com/whatwg/html/pull/4031#discussion_r245259907), is it unnecessary to Fetch in parallel? Also, is it possible that we might not be able to determine if response is a network error until later on (since response isn't done yet)? |
| 03:04 | <Domenic> | You have to fetch in parallel; it does network I/O which you can't do on the main thread |
| 03:04 | <Domenic> | Otherwise it's similar to JS. The `response` variable does not have a full body, but it has headers, you'll know if it's a network error, etc. |
| 03:05 | <domfarolino> | Ah ok gotcha |
| 03:35 | <domfarolino> | Uh, is https://drafts.csswg.org/ down for anyone else? |
| 03:40 | <Domenic> | Works for me |
| 03:42 | <domfarolino> | :( |
| 19:09 | <Domenic> | domfarolino: I don't really understand your proposal at https://github.com/whatwg/html/pull/4031/files#r247760518 |
| 19:12 | <domfarolino> | Domenic: My impression was you wanted all of the steps from "Let <var>success</var> be true" and down, moved to the process response task, which in the current state, seems analogous to the process the linked resource steps |
| 19:13 | <Domenic> | Oh, no, I gave the wrong impression then |
| 19:13 | <domfarolino> | I was thinking of moving said steps into that algorithm, but moving the "fetch/wait for critical subresources" into link stylesheet's override of process the linked resource |
| 19:13 | <domfarolino> | Ah ok |
| 19:13 | <Domenic> | I think it's fine as-is, it's just worth noting that you don't get the response body unless you explicitly use the phrase "process response body" or something like that. And we need the response body for the critical subresources. |
| 19:14 | <Domenic> | But I think that's all details we don't need to fix right now. |
| 19:14 | <Domenic> | Although, hmm, this might all be simpler if you just set the synchronous flag |
| 19:15 | <domfarolino> | Was wondering if that would be reasonable since we're in parallel |
| 19:15 | <Domenic> | Yeah let's do that |
| 19:16 | <domfarolino> | Ok, I'll do that and add a warning about critical subresource fetching being underdefined, and maybe mention how it should be taken care of by another spec (CSS for example I guess). |
| 19:17 | <domfarolino> | Although, that seems to imply that load/error events won't be fired until the entire response is available right? |
| 19:18 | <domfarolino> | Oh, I guess that's how it is defined currently too "Once the attempts .... are complete" |
| 19:20 | <domfarolino> | Using process response would be nice eventually though I think |
| 19:25 | <Domenic> | I'm not sure there's a difference between async + process response vs. sync flag + just do the steps, besides a level of indentation |
| 19:31 | <domfarolino> | Right, I do like the idea of using process response though mostly just because it exists |
| 21:03 | <domfarolino> | Domenic: OK I'd say 4031 is ready for re-review now |
| 23:53 | <devsnek> | mfw the html spec is almost 6mb |