00:41 | <Maxim Vaarwel> |
How can I find out what these APIs are affect to the DOM and not decorated with [CEReactions] ? Could anyone provide some example of such an API? |
08:01 | <annevk> | I think I did all the WHATNOT call follow-up stuff now. Panos Astithas if you notice something missing please let me know. |
11:32 | <annevk> | Seems JSON has quite a few interop issues: https://www.mlsec.org/docs/2024b-asiaccs.pdf |
11:57 | <sideshowbarker> | > our analysis shows that the effects of an imprecise specification can hardly be resolved at the implementation level |
12:45 | <annevk> | Not entirely convinced by that part of the paper, but the interop issues seem real |
12:46 | <annevk> | For instance, one of the references to back that up is https://seriot.ch/projects/parsing_json.html which doesn't consider the Ecma document and the main complaint is about it not defining things around limits, though I can see how for numbers that does present a bit of an ordeal |
13:27 | <evilpie> | I think it's quite telling that v8 and SpiderMonkey don't have interop issues according to their matrix (figure 6) |
21:12 | <smaug> | dbaron: what is https://searchfox.org/mozilla-central/rev/4e0f4c612589c23344f22285520a44a3f45c9e6e/testing/web-platform/tests/html/semantics/interactive-elements/the-details-element/name-attribute.html#198-200 trying to test? |
21:13 | <smaug> | That should, in theory, trigger more mutation events, since it is just calling setAttribute in another (mutation) event listener |