| 08:16 | <Noam Rosenthal> | annevk, Jake Archibald, how would you like to proceed with https://github.com/whatwg/fetch/pull/1329? annevk you've raised some questions about how this would apply to worker, I think all answers are valid but want to proceed somehow |
| 09:29 | <annevk> | Noam Rosenthal: I'm under the weather this week, but I think we need to tackle the service worker part as well; there's not many hits for "terminate" in SW, but there's a few and we cannot just break the system |
| 09:29 | <annevk> | Noam Rosenthal: putting a Living Standard in an inconsistent state is not something I'm happy with if it can be avoided |
| 09:29 | <Noam Rosenthal> | annevk: hope you get well soon :) |
| 09:31 | <Noam Rosenthal> | annevk: Currently SW references the somewhat handwavy "when the Fetch is terminated" which is an exported link that is still going to be there, I don't think we're leaving it more inconsistent than before. But I don't mind posting a PR to SW that makes it explicit with a controller, if that's the direction |
| 09:34 | <annevk> | Noam Rosenthal: yeah, that sounds good to me still. I wish others would chime in a bit more or at least say something to the effect of "sounds reasonable, can't think of anything better". |
| 09:35 | <Noam Rosenthal> | annevk: cool, I'll propose the PR, and hopefully it would be enough of a strawman to get some "sounds reasonable" or "let's do this differently" |
| 12:19 | <Noam Rosenthal> | annevk: I thought as an alternative to returning a controller, to emit an "onFetchStarted(controller)" from both fetch and SW. This way the processes as they are today don't need to change and everything can still work. It might make my patch quite simpler. WDYT? |
| 12:20 | <Noam Rosenthal> | ... otherwise I need to turn HTTP fetch into something that "awaits" fetch or make a lot of changes in fetch to make internal algorithms asynchronous |
| 12:21 | <zcorpan> | I vaguely remember discussing something along those lines with zcorpan . I don't recall any reported breakage from Gecko fixing that. |
| 14:36 | <Noam Rosenthal> | annevk: I thought as an alternative to returning a controller, to emit an "onFetchStarted(controller)" from both fetch and SW. This way the processes as they are today don't need to change and everything can still work. It might make my patch quite simpler. WDYT? |
| 20:31 | <Dominic Farolino> | https://fetch.spec.whatwg.org/#concept-scheme-fetch mentions "URLs such as "about:config" are handled during navigation and result [...]" Where exactly are these URLs handled in navigation? |
| 20:44 | <Andreu Botella (he/they)> | https://fetch.spec.whatwg.org/#concept-scheme-fetch mentions "URLs such as "about:config" are handled during navigation and result [...]" Where exactly are these URLs handled in navigation? |