| 07:27 | <Kaiido> | Relatively interesting question about <link> processing (which stays a bit unclear to me): https://stackoverflow.com/questions/76319964/what-is-the-behavior-of-a-link-with-both-preload-and-stylesheet-in-rel-attribute Maybe Noam Rosenthal could shed some light on this? |
| 07:28 | <Kaiido> | Also I noticed that https://html.spec.whatwg.org/multipage/links.html#link-type-preload has a link to [PRELOAD] which actually redirects back to https://html.spec.whatwg.org/multipage/links.html#link-type-preload since W3C Preload has been merged to HTML. I find it kind of funny to have such a recursive link inside the link.html page, but maybe we want to do something about it? There is still value in this link since it does give credits to I. Grigorik for their work. Is it worth an issue? |
| 07:35 | <Noam Rosenthal> | Relatively interesting question about <link> processing (which stays a bit unclear to me): https://stackoverflow.com/questions/76319964/what-is-the-behavior-of-a-link-with-both-preload-and-stylesheet-in-rel-attribute Maybe Noam Rosenthal could shed some light on this? |
| 07:38 | <Noam Rosenthal> | Relatively interesting question about <link> processing (which stays a bit unclear to me): https://stackoverflow.com/questions/76319964/what-is-the-behavior-of-a-link-with-both-preload-and-stylesheet-in-rel-attribute Maybe Noam Rosenthal could shed some light on this? |
| 07:39 | <Noam Rosenthal> | S/Rhys/this |
| 07:40 | <annevk> | We should remove [PRELOAD] and add I. Grigorik to the acknowledgments if they aren't already there |
| 07:40 | <annevk> | I suspect they are there |
| 07:43 | <Kaiido> | Noam Rosenthal: thanks, that confirms my own thoughts then. annevk so a PR directly would be preferable? I probably won't have the time myself to do so today so it might be better for someone else to lead this. |
| 07:44 | <Noam Rosenthal> | Noam Rosenthal: thanks, that confirms my own thoughts then. |
| 07:45 | <Kaiido> | I opened https://github.com/whatwg/html/issues/9327 |
| 10:12 | <Noam Rosenthal> | I opened https://github.com/whatwg/html/issues/9327 |
| 12:34 | <freddy> | Why does the policy container (https://html.spec.whatwg.org/#policy-containers) contain the CSP, referrer policy and embedder policy but not the sandbox flags? |
| 12:46 | <annevk> | freddy: it's very much an incremental effort, if you think things should be added, go for it |
| 12:55 | <freddy> | heh, I now realize there is a big red box that even says it 🫢 |
| 13:02 | <Ms2ger> | Nothing as easy to miss as a big red box 😅 |
| 14:40 | <Dominic Farolino> | Another promise and "parallel" question. I believe you cannot "react" to a Promise from in parallel, right? I.e., call "Upon fulfillment" on a promise from steps running in parallel. |
| 14:42 | <Ms2ger> | That's correct |
| 14:48 | <annevk> | Dominic Farolino: you gotta think bigger, you cannot manipulate JS objects in parallel to some event loop, period |
| 16:42 | <TabAtkins> | Nothing with observable effects can be done in parallel. (Except posting a task itself, which I suppose produces observable timing differences?) |
| 17:27 | <annevk> | TabAtkins: yeah, though you still get some guarantees if things go into the same task source |
| 17:28 | <annevk> | And yeah, exactly, you want to do state updates from steps in a task. |
| 17:44 | <Dominic Farolino> | Yep I just wanted to sanity check |