| 00:28 | <sideshowbarker> | PSA: #web-platform-dx:matrix.org is a newish relevant room that’s a piece of an ongoing effort “to improve the overall experience of developing for the Web platform” — in part by “enabling shared research on the pain points that developers face” https://www.w3.org/blog/2022/11/webdx-improving-the-experience-for-web-developers/ has an overview |
| 12:24 | <Ondřej Žára> | Hmm, do I understand correctly that there is no longer a way to send a full Referer (incl. path) on a cross-domain request? |
| 12:25 | <Ondřej Žára> | (even if both parties - both origins - agree that it is a good idea in this particular scenario) |
| 13:37 | <Domenic> | I think it's possible per spec using referrer-policy: unsafe-url. I think Safari decided to ignore this, so for them you have to use a query string or something. |
| 13:43 | <Ondřej Žára> | Hmm, I tried this in Firefox (via <meta>). And received: Referrer Policy: Ignoring the less restricted referrer policy “unsafe-url” for the cross-site request |
| 19:54 | <Andreas Kling> | Domenic: Heyo :) In "prepare the script element" step 32.1, we assert that el's result is "uninitialized". it seems to me that el's result could be e.g "null" at this point if "fetch an inline module script graph" returns early in step 31. Does that sound about right? |
| 23:59 | <Domenic> | Andreas Kling: yeah, that does sound right. Hmm, is there any better fix than just removing the assert? |