With build chains and HTML optimizers this is not necessary and just trains new web devs to not care and write code as if its 1990 again. Well-formedness is a new concept introduced by [XML]. XHTML 1.0 (this specification) is the first document type in the XHTML family. Thats the simple story. The following example shows the way in which XHTML 1.0 could be used in conjunction with the MathML Recommendation: The following example shows the way in which XHTML 1.0 markup could be incorporated into another XML namespace: A conforming user agent must meet all of the following criteria: White space is handled according to the following rules. I think XHTML was too strict and put a high cost for a low gain, but it had point. Some input types have a default minimum. This is the same issue you have when you add newlines in places with s which are styled by css and you get visual spacings between elements you didnt want.

here is an emphasized paragraph.

,

here is an emphasized paragraph.

. XHTML is a family of current and future document types and modules that reproduce, subset, and extend HTML4 [HTML4]. As we included an invalid value, supporting browsers will show the value as invalid. White space handling in attribute values isnt done according to XML. The XHTML entity sets are the same as for HTML 4, but have been modified to be valid XML 1.0 entity declarations. (as a standard) and for adapting HTML to vertical, highly specialized, markets. Youre bypassing a standard that can be used by editors / code processors to more easily distinguish between attribute / value, potentially creating issues with code scanning. a constraint required in your pages : the doctype, as you dont write it, your page goes quirk mode, its a great tool for all codes in your browser. Script and style elements dont need CDATA sections. I just fixed the library to generate tags and it solved the problem. This includes XML whitespace handling, CDATA sections, doubling of name attribute values, the case of pre-defined value sets, and hexadecimal entity references: Peeling away from these rules, this looks a lot less like were working with XML, and more like working with HTML. corresponding items attribute requirements or the location allowing mixing of attributes. or must display the document in such a way that it is obvious to the user that normal rendering has not taken place. Consider this case: Its not intuitive what the result should be. In XML, fragment identifiers are of type ID, and there can only be a Rediscover HTML, and help shape a new, modern way of writing HTML which acknowledges, but isnt necessarily based on XML. The XML document object model specifies that element and attribute names are returned in the case they are specified. Oof. Script and style defined in the W3C Recommendation for HTML4. Note that this recommendation does not define how HTML conforming Next within the remaining possibilities, collecting personal data should be minimized. In addition, browsers ignore errors in HTML But were not done yet. And while the use of extension elements isnt as bad as before HTML4/5 standards, it still has to be accounted for. Youre introducing possible fail-points in your HTML, making maintainability a potential issue. No one ever made a slow website into a fast one by leaving out closing tags. the type attribute of the input element). explicitly address the issue of whitespace handling in non-Latin character sets. Note that XML parsers are permitted to silently remove the contents of comments. Perhaps some of them make your code more readable too. In the 2000s, there was XHTML. Everyone wants an edge during the N.B.A. Use external scripts if your script uses < or Consistency is a lot easier than special rules. The following example shows the difference