| 11:44 | <freddy> | side question for the AsyncContext proposal collaborators: anyone know if the iframe load event bug in Firefox has been filed somewhere? I'm not sure the prose text here provides sufficient information for it to be actionable. |
| 12:02 | <freddy> | Not urgent, but for visibility nicolo-ribaudo ----^ |
| 12:05 | <Andreu Botella> | from what I'm seeing, there was some discussion about possibly adding the error event to the spec in https://github.com/whatwg/html/issues/1518 |
| 12:06 | <Andreu Botella> | i have no opinion about whether firefox should keep the event, or whether it should be spec'd – but if it stays it should interact with AsyncContext the same as load |
| 12:29 | <Tom Schuster> | Noam Rosenthal: Where would I put a question for your includes proposal? |
| 12:30 | <Noam Rosenthal> | https://github.com/wicG/declarative-partial-updates/ |
| 12:30 | <Noam Rosenthal> | I will move it to a new WHATWG issue soon that includes the proposal as the existing client-side include issue has 100s of comments |
| 12:32 | <Noam Rosenthal> | The existing explainer is https://github.com/WICG/declarative-partial-updates/blob/main/fragment-include-explainer.md so you can refer to it |
| 12:39 | <evilpie> | Thanks |