3 ms·
I highly recommend everyone involved in web development to read at least a small proportion of the horrors that are the HTML parser specification. It will leave
by notnullorvoid 8mo ago
I highly recommend everyone involved in web development to read at least a small proportion of the horrors that are the HTML parser specification. It will leave you yearning for the return of XHTML.
Or you could also read web proposals where the reason for avoiding the ideal implementation is complication of updating HTML parser rules.
Or attempt to use the web features that are already hindered by the HTML parser (custom element table rows).
- jraph 8mo ago> It will leave you yearning for the return of XHTML. …or be grateful you can just use an existing HTML5 parser that hides all this stuff to your innocent eyes :-)
- notnullorvoid 8mo agoGrateful in part, but I can't help to think that if there was refusal to build parsers for an outlandish spec in the first place then we'd have fixed the problem by now. Using existing parsers only hides the poor design up to a point.
- jraph 8mo agoI'm conflicted on this. I mostly agree with the sentiment, I'd rather have simple parsers and sensible specs, but I'm also happy they do whatever it takes not to break anything (well, they are breaking XSLT…)
- yomismoaqui 8mo agoNowadays you can use AI to write the parser, so it's the machine the one that suffers I guess. https://friendlybit.com/python/writing-justhtml-with-coding-agents/ https://friendlybit.com/python/writing-justhtml-with-coding-...