| 11:49 | <smaug> | does anyone else but Gecko support nested workers? |
| 11:49 | <smaug> | Or did blink add support in case there is service worker which wants to use normal workers or something? |
| 11:50 | <smaug> | (though, I don't understand the lifetime management of subworkers in that case) |
| 12:58 | <jyasskin> | smaug: I know blink talked about letting SWs use normal workers, but I don't know the outcome. |
| 13:28 | <Domenic> | smaug: IIRC Blink wants to but hasn't devoted the resources yet... |
| 13:30 | <smaug> | Domenic: right. I also wonder how to have reasonable lifetime for subworkers when SW can be killed at any time |
| 13:40 | <annevk> | smaug: GC-lifetime :-p |
| 13:45 | <beverloo> | annevk, friendly ping re: https://github.com/whatwg/notifications/pull/82, as you asked :) |
| 13:51 | <Domenic> | https://html.spec.whatwg.org/#execute-the-script-block can anyone tell how to write a test that the last step queues a task to fire load, vs. does not? |
| 14:11 | <Domenic> | Filed https://github.com/whatwg/html/issues/1817 if someone wants to help |
| 14:37 | <jgraham> | Domenic: It *might* work to add a second script block after the first that added a load event listener. If load is fired synchronously that script would never see it, otherwise it almost certainly would |
| 14:37 | <jgraham> | But that seems potentially racy |
| 14:38 | <jgraham> | Or maybe you can use postMessage |
| 14:39 | <jgraham> | If you see the load before a postMessage at the end of the script block it must have been sync, otherwise it was async |
| 14:40 | <jgraham> | If they use the same task source… |
| 14:42 | <annevk> | beverloo: I tried to ping someone internally |
| 14:42 | <annevk> | beverloo: so, one more week? |
| 14:42 | <annevk> | beverloo: I mean, I tried pinging someone again |
| 14:44 | <beverloo> | annevk, sure, I appreciate that! It's a bit of a systematic issue though, it would be great to see more involvement from your notifications people in general |
| 14:46 | <smaug> | mkwst: are you still somewhere around @tpac |
| 15:01 | <annevk> | beverloo: there's only one at the moment as far as I know and he's doing other things |
| 15:10 | <smaug> | mkwst: https://bugs.chromium.org/p/chromium/issues/detail?id=649686 |
| 16:23 | <smaug> | how does one get email about all the new topics in discourse.wicg.io |
| 20:02 | <annevk> | beverloo: change is fine with wchen |
| 20:03 | <annevk> | beverloo: guess I can merge next week, but there's also a small outstanding comment |
| 20:03 | <annevk> | beverloo: I suppose I could also check the whole text one more time |
| 22:26 | <smaug> | are there any wpt tests for secureContext? |