| 02:47 | <EveryOS> | I noticed that the DOM Standards embeds all covered IDL into the index (#idl-index) while the HTML spec just links to covered IDL in the index (#all-interfaces). I take it that is because the HTML spec defines so many more interfaces than the DOM spec? |
| 19:09 | <EveryOS> | Java's org.w3c.dom package is way out of data. |
| 19:09 | <EveryOS> | For example, Java includes a method called `isSupported` |
| 19:09 | <EveryOS> | https://docs.oracle.com/en/java/javase/14/docs/api/java.xml/org/w3c/dom/Node.html#isSupported(java.lang.String,java.lang.String) |
| 19:09 | <EveryOS> | However, the DOM specification specifically says *not* to support this method |
| 19:09 | <EveryOS> | https://dom.spec.whatwg.org/#dom-node-issupported |
| 19:13 | <EveryOS> | Unless the w3c specs and the WhatWG specs conflict |
| 20:17 | <EveryOS> | So from my understanding, if I had a Element whose children were Text, Element, Text, and Element's children was Text, the Element's Text child would be ignored, but the other two text elements would be concatenated? https://usercontent.irccloud-cdn.com/file/Rmp7fEvt/image.png |
| 20:21 | <EveryOS> | Like this https://usercontent.irccloud-cdn.com/file/gPRhoxqW/image.png |
| 21:01 | <EveryOS> | Afk, I'll see if there is a response later |
