Also see the XMLC 2.2 Release Note, XMLC 2.2.1 Release Note, and XMLC 2.2.2 Release Note.
Added further XHTML workarounds when using OutputOptions#setEnableHTMLCompatibility(boolean). Previously, we only forced end tags on <script>. This was because IE had problems with Javascript when using the minimized version (eg... <script src="myscript.js" />). However, it also seems that HTML parsers have difficulty parsing tags which are minimized, but are defined in the dtd as having a non-empty content model (eg... <div id="myid" />). In these cases, an HTML parser sees this as a start tag, not a start+end tag. Forcing all tags with a non-empty content model to have an end tag solves this issue. Note that in Mozilla, this is only a problem when serving the document as text/html. The XML parser is used for application/xhtml+xml. Of course, IE doesn't understand the latter mime-type, so for compatibility, text/html is necessary.
Also made sure that, in minimized tags, a space is added before the slash (eg... <br /> rather than <br/>)
See here for more info: