Interesting fact: Firefox (or Gecko to be accurate, because there was no single “Firefox” browser back then - there was Netscape Navigator and Mozilla Application Suite) had such rendering mode, but it was quickly abandoned.[1]
https://hsivonen.fi/doctype/: “In the summer of 2000 before Netscape 6 was released, Gecko actually had parser modes that enforced HTML syntax rules and one of these modes was called the “Strict DTD”. These modes were incompatible with existing Web content and were abandoned.”
This wsa considered in the earlier days of the web, but then intentionally not enforced. HTML was specifically designed to not fall into the same scheme as most programming languages in that it should try to render what it could even if there was a lot going wrong (unlike most programming languages that try to fail fast).
(And before someone comes after me for comparing HTML to programming languages, I am well aware that it is not Turing complete.)
Works is different from works consistently across all browsers, or even versions of the same browser. I know most web developers got into their heads that only Chrome (and maybe Firefox if they are feeling generous) matters, but open source projects shouldn’t incentivise this.
Could bring that up with the devs but it hasn’t been the early 2000s for a long time, nobody seems to care as long as it works.
Which is a shame. Browser should be strict when rendering.
Interesting fact: Firefox (or Gecko to be accurate, because there was no single “Firefox” browser back then - there was Netscape Navigator and Mozilla Application Suite) had such rendering mode, but it was quickly abandoned.[1]
XHTML.
I choose to imagine that these offenses result in developers cooling their heels in the slammer rather than a browser being a picky eater.
This wsa considered in the earlier days of the web, but then intentionally not enforced. HTML was specifically designed to not fall into the same scheme as most programming languages in that it should try to render what it could even if there was a lot going wrong (unlike most programming languages that try to fail fast).
(And before someone comes after me for comparing HTML to programming languages, I am well aware that it is not Turing complete.)
Works is different from works consistently across all browsers, or even versions of the same browser. I know most web developers got into their heads that only Chrome (and maybe Firefox if they are feeling generous) matters, but open source projects shouldn’t incentivise this.