3 ms·

xhtml was never supported by all major browsers. You couldn't do stuff like <div/> and get away with it. Not sure why the the self closing tags became widely u

• mjhagen 5y ago
  Some editors had trouble with color coding non-compliant xhtml. At least that was my reason for doing it. (In the very early 2000s)
• progval 5y ago
  > xhtml was never supported by all major browsers. Source? https://caniuse.com/xhtml https://caniuse.com/xhtml says otherwise > You couldn't do stuff like <div/> and get away with it. I just tried on both Firefox and Chromium, they parse it properly.
  • jontro 5y ago
    When xhtml was popular internet explorer was a major blocker for using it properly. I never saw xhtml served with the proper content type at the time. I don't see a reason to mix html and xhtml today. It will only lead to problems. (I.e using self-closing tags and &amp; mismatches in urls) If you use <div/> in html the browser will just ignore the end / See https://jsfiddle.net/sw8j9fo2/ https://jsfiddle.net/sw8j9fo2/
    • deleted 5y ago
      [deleted]
• wwweston 5y ago
  > Not sure why the the self closing tags became widely used For a while adhering to the open/close conventions helped use tooling / libraries built around the assumptions for XML in dealing with HTML, maybe up through the late 00s/early 10s. Any utility gains there faded as HTML5 conventions and libraries became more solid, but I still have a bit of the habit, especially with <img/> & <br/>.