2 ms·
Most browsers have quirks modes for different types of HTML standards. Certain errors are renderered in certain ways because that's what web devs used to expect
by jeroenhd 5y ago
Most browsers have quirks modes for different types of HTML standards. Certain errors are renderered in certain ways because that's what web devs used to expect, even if they weren't following the standard. If you strictly enforce XHTML1.1 or HTML4 because the website says that's the standard it follows, you end up with tons of broken websites. It's a consequence of websites historically being lenient with front end developers.
The HTML5 string basically says "I promise to be good, please turn off your weird workarounds". Of course, HTML5 has been around long enough that some browsers still have certain quirks, but they're not as extensive as the ones before HTML5.
Compared to the `<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd http://www.w3.org/TR/html4/loose.dtd">` monstrosity from before, I'll happily take the modern standard. There's no version number anymore, just a simple HTML identifier.