alt Hacker News> The alternative is parsing failure on improperly nested HTML which I don’t think is desirable.
It was that decision that resulted in the current mess. Browser vendors could have given us a grace period to fix HTML that didn't validate against the schema. Instead they said "there is no schema"
The issue as I see it is that XML schemas are fine[0] for immutable documents but not suited for dynamic content. As a user it would be extraordinarily frustrating for a site or web app to break midflow because of a schema validation failure after a setHTML call or something.
[0]: I’ve worked with XML schemas a lot and have grown to really dislike them actually but that’s neither here nor there