2 ms·
Browsers literally would not render with one tiny syntax error/spec-deviation in your HTML No different than having a JSX syntax error in React today
by vmception 4y ago
Browsers literally would not render with one tiny syntax error/spec-deviation in your HTML
No different than having a JSX syntax error in React today
- Macha 4y agoIn XHTML strict mode, which basically nobody used. In XHTML transitional, and HTML1-4, what you'd get is browsers with divergent understandings of your DOM tree structure such that content that worked fine in one would be a horribly mangled mess (often breaking layout in difficult to read ways) in another browser.
- wwweston 4y agoSome of us tried XHTML. A little bit of extra consistency in syntax and closed tags was rewarded with being able to use tooling built around XML expectations. I dug that. And then I found out there were some browsers that wouldn't handle it right unless content-type headers were set up right on the server, and of course that made it an extra pain, especially on commodity hosting where you might not have that remotely under your control. The "strict warnings"/"rendering problems crash the page" setting was also... mixed. Certainly prompted you to pinpoint the issue and fix it but that level of nag often felt unnecessarily militant after what everyone was used to.