| 00:18 | <mel00010> | I've been working on implementing an entirely new HTML layout engine, and up until recently was blissfully unaware of the fork of the HTML specification between the W3C and WHATWG. So far, I have been following the W3C HTML5 specification. After some research, I have decided to follow the WHATWG specification instead, as it appears more authoritative. I've only implemented the tokenization stage of parsing and some of |
| 00:18 | <mel00010> | the common microsyntaxes so far. Are there any serious differences (things I should re-implement) between the specifications that I should be aware of? |
| 00:18 | <mel00010> | Sorry if this is the wrong place for this question BTW |
| 00:21 | <mel00010> | Also, this is an independent project, mostly for fun and to learn the specification inside out |
| 01:17 | <Domenic> | mel00010: https://diffofhtmls.herokuapp.com/ should help. Glad to hear you found your way to the right place :). |
| 01:29 | <mel00010-mobile> | Thanks. This fork issue is really annoying. It defeats the whole point of standards |
| 05:39 | <GPHemsley> | mel00010: I don't think you'll find anyone here who will disagree with you on that point ;) |
| 07:42 | <MikeSmith> | SimonSapin: about https://github.com/whatwg/html-build/issues/144 I wonder if the dfn backlink behavior works for you |
| 07:44 | <MikeSmith> | that is, the behavior where if you click on the text of a dfn’ed term, a pop-up is shown with all the places in the space that reference that term |
| 07:47 | <MikeSmith> | regardless, I think that message indicates you need to rebuild your wattsi binary from the latest sources |
| 07:49 | <MikeSmith> | because wattsi is what generates that xrefs.json file, but it’s only been doing that since June |
| 07:49 | <MikeSmith> | https://github.com/whatwg/wattsi/commit/b57d52cef308e8e3b249034d314e19ee6e3a824a |
| 07:50 | <MikeSmith> | so if you’ve not rebuilt your wattsi after June, then it’s not generating that expected xrefs.json file |
| 07:51 | <MikeSmith> | I guess we should probably add some code to the build script to catch that case and emit a message saying “You need to rebuild your wattsi” |