| 11:59 | <nicolo-ribaudo> | DomenicDo you mind if I start working on https://github.com/whatwg/html/issues/7996? It took me a while to understand how "wait until it asynchronously complete" and "custom perform the fetch steps" work, and I would be happy to help replacing them with more explicit constructs. |
| 12:24 | <Andreu Botella> | Has anyone else noticed that HTML's section on "killing scripts" only focuses on killing script or module evaluation, rather than the evaluation of a callback? |
| 12:59 | <Domenic> | DomenicDo you mind if I start working on https://github.com/whatwg/html/issues/7996? It took me a while to understand how "wait until it asynchronously complete" and "custom perform the fetch steps" work, and I would be happy to help replacing them with more explicit constructs. |
| 13:00 | <hsivonen> | annevk: FWIW, it looks a lot like https://github.com/web-platform-tests/wpt/blob/master/html/cross-origin-embedder-policy/non-initial-about-blank.https.html passes in Gecko for the wrong reason. |
| 13:01 | <hsivonen> | As for pass in other browsers, I'm currently trying to locate spec text that would explain why going from lack of src to src="about:blank" should trigger a navigation from the initial about:blank to a non-initial about:blank. |
| 13:09 | <hsivonen> | So, I take it that a change in src triggers a navigation even if the URL resolves to the same URL that's already the URL of the current doc in the iframe. |
| 13:44 | <zcorpan> | hsivonen: https://html.spec.whatwg.org/multipage/iframe-embed-object.html#the-iframe-element:process-the-iframe-attributes-3 |