> Some authors find it helpful to be in the practice of always quoting all attributes and always including all optional tags, preferring the consistency derived from such custom over the minor benefits of terseness afforded by making use of the flexibility of the HTML syntax. To aid such authors, conformance checkers can provide modes of operation wherein such conventions are enforced.
In the other words it recognizes the benefit from explicit tags, but also recognizes the benefit from optional tags. So they are equally conforming.
At the end of the day, HTML's flexibility as a markup language is what made it popular and usable by anyone, and ambiguity is the price we pay for it.
These days the DOM semantics are even less important as everything is done in JS anyway for all but the simplest documents
(START div)Hello (START b)world\b/!\div/
why ever you would want this.But despite all the flexibility offered by SGML and because probably nobody implemented HTML parsing by using a SGML parser, we ended up with malformed HTML documents who's interpretation was essentially defined by whatever the ad hoc HTML parser implementations in browser did.
HTML5 finally abandoned the idea of basing HTML on SGML and a DTD and instead essentially formalized the status quo of HTML parsing and put it into the specification. At least this is my understanding as a non-web developer who gets to work with HTML only occasionally.
The W3C was too strict where it didn't really matter (the basic markup) and too loose where it did matter (everything else).
Also there was no specification right from the start and the feature set was very limited, so that everyone started implementing their interpretation of HTML and adding their extensions. Trying to combine and standardize all the things existing in the wild would necessarily be a hard task. Many early extensions were probably also quite ad hoc and even if not they most likely did not take into account interactions with extensions from others.
But in the end this could probably never have happened much differently, future developments and requirements could not known in any detail and even if nobody would ever have spent a decade to write good specifications for a new technology which might or might not get adopted.
The things that did try to design for the future, across platforms, failed. Java on the desktop, WPF, etc. all gave way to the simplicity of web technologies.
Developers?
In the early days of the web it wasn't developers writing HTML. It was anybody who wanted to publish anything on the web. Real programmers didn't touch it. That is why browsers had to be tolerant of bad code.
Exactly. The parser is designed to parse documents, not code. The document has a structure (like sections, paragraphs, tables, etc). When the structure doesn’t quite make sense, the parser still displays the content (the blog, story, words, etc).
> But was this worth it, could better tooling not have achieved the same with good error messages helping to fix errors?
You need to think about compatibility, especially backwards compatibility. If the standard was so strict that any error resulted in the browser rejecting to parse the document, then as the specification evolved every website would need to be updated. The lack of constraints around standards also means that different browsers can evolve and implement different features at different cadences.
What is the end result? Nothing for the end user, they do not care whether the browser has to deal with nice HTML or a mess. Developer writing HTML get to be more sloppy at the price of a lot of additional complexity and pain where ever code has to deal with HTML. This might actually have some negative impact on end users because of bugs or security issues stemming from the additional complexity. Maybe it made HTML somewhat more accessible to the casual user as they could get away with some mistakes. But was this worth it, could better tooling not have achieved the same with good error messages helping to fix errors?