| 08:28 | <annevk> | sunil: I don't know. |
| 08:40 | <annevk> | sunil: I think you're correct that it's supposed to work although I'm not sure to what extent we actively considered shared/service workers at the time. I don't recall. |
| 08:42 | <sunil> | Thanks annevk, Do you know who could have more idea on this? |
| 08:45 | <sunil> | annevk: I am implementing this in Firefox and trying to check if it would be helpful to extend the wpt to service workers as well. It wouldn't add much value if other browsers do not fully support it for workers though. |
| 09:35 | <Domenic> |
|
| 10:06 | <annevk> | sunil: I suspect the most straightforward way to find out is to write those tests and run them |
| 10:07 | <sideshowbarker> | These numbers seem pretty believable to me. |
| 11:03 | <sideshowbarker> | About the test at https://wpt.fyi/results/inert/inert-and-find-flat-tree.html — |
| 11:04 | <sideshowbarker> | correction: Is “Text slotted into a dialog which is inside a shadowroot” defined as inert? |
| 11:10 | <sideshowbarker> | Luke Warlow: ↑ (if you happen to know — since I think you may have recently been working on something that you were running the inert test cases to check against) |
| 11:18 | <Luke Warlow> | Apologies I'm not sure about that, I think the inert test I was looking at was using a test driver API that was changed. So it was tangential to the inert spec |
| 19:16 | <elf-pavlik (elf Pavlik)> | Hello, what would be equivalent in browser's fetch to what nodejs undici supports with dispatcher: new Agent({ bodyTimeout: 0 }). This way one can disable the default 300s body timeout.I have an example of long lived streaming responses which I would also like to have working in the web browser https://github.com/elf-pavlik/sosy24/blob/main/streaming-http.mjs |
| 19:18 | <elf-pavlik (elf Pavlik)> | relevant undici docs https://undici.nodejs.org/#/docs/api/Dispatcher?id=parameter-dispatchoptions |