| 04:42 | <sideshowbarker> | https://ladybird.org/posts/adopting-rust/
|
| 16:49 | <annevk> | Hey Luke Warlow I was curious if we finally solved the script issue seeing https://github.com/whatwg/html/pull/12195 up? |
| 17:35 | <Luke Warlow> | We have not yet unfortunately. This is mostly to fix Typescript definitions. |
| 17:38 | <annevk> | I see, I suppose that might be acceptable, but I want to look at the situation again. Do we have some visible XXX markers already? |
| 17:39 | <Luke Warlow> | https://w3c.github.io/trusted-types/dist/spec/#setting-slot-values-from-parser - yeah we have some here. None in the HTML spec yet. |
| 17:42 | <Luke Warlow> | The main thing is still that we need the children changed steps to provide the cause of the change aka API vs parser. But that's unfortunately not something I have time to take on myself. |
| 18:27 | <Lea Verou> | Does anyone remember why DOMException#code was deprecated? It came up in a TC39 breakout today |
| 18:47 | <Noam Rosenthal> | FWIW The DOM spec calls them "legacy codes" and marks some of them as deprecated |
| 18:48 | <Lea Verou> | The context was this proposal that will be presented at the upcoming TC39 meeting in NYC next month and whether this is a blocker: https://github.com/jasnell/proposal-error-code-property But the conclusion was that DOMException could always define its own .code that behaves differently. |