| 06:06 | <annevk> | daxpedda: yes, that's a good first step. See https://whatwg.org/working-mode#changes for the complete list of tasks. You can consider WebKit to be supportive of such a change. |
| 08:52 | <nicolo-ribaudo> | Is there a public calendar I can subscribe to for whatwg meetings, like there are for w3c working groups and for TC39? For some reason in all the email clients I use I have to manually accept the updates for them to be reflected in my calendar, which causes issues every time there is a change 😅 |
| 09:39 | <foolip> | keithamus: you asked about font enumeration. I couldn't find a demo, so I built https://foolip.github.io/font-enumeration-demo/ to show this working with pixel readback with canvas already. |
| 09:41 | <keithamus> | Thanks for this |
| 13:51 | <Nick Sloan> | annevk: I'm the person who requested https://github.com/whatwg/html/issues/12290. I think at a higher level, this is about a gap in parity between declarative and imperative code related to form submissions. Maybe parity isn't a goal at all, but I think it ought to be. If I can change a form's behavior with a button in the DOM, I ought to be able to do the same without a button. |
| 13:54 | <Nick Sloan> | Thanks for engaging on the issue, by the way. |
| 15:20 | <Dominic Farolino> | Callback interfaces are discouraged, but if I was designing an API that took an object and called a method on it that needs proper this binding, should that API just take a normal interface object,and call the methods by name on it, kind of like how custom element lifecycle callbacks are invoked? Edit: actually I guess the magic is just supplying the right callback this value... |