I just loaded the ModX plugin. Thanks!

Consider this comment:

<!--[if gte IE 5.5000]>
     <script type="text/javascript" src="foo.js"></script>
<![endif]-->

That entire block gets stripped if set to remove HTML comments, and of course that means IE5+ doesn't see the script it needs. Can you think of a way to avoid removing these specific comments, or perhaps some other way to do the conditional logic which avoids this specific problem?

For my purposes I'll see if I can fix the JS so that when it's included by IE it performs properly.

I will also probably activate the plugin that tells visitors that they need IE6+. But this issue with conditional comments is interesting nonetheless...
Thanks.

Hi !

I now develop with HTML5 and XHTML Beautify don't consider the unecessary final slash for balise meta, link, img, br or hr

Do you think to make a "HTML5 Beautify" for MODx ? :)

Extension update fails due to naming differences?

Rename namespace and references to 'xhtmlbeautify' instead of 'htmlbeautify'.

Inline JavaScript tags are getting converted to entities by htmLawed.

When used together with Formit, Formit was not able to to complete its processing.

When using Articles and its subpackages, the taglist navigation and paging don't work anymore. If I deactivate the XHTML Beautify plugin, the navigation works again.

Running on:
MODX 2.2.4 traditional
XHTML Beautify 1.0.2-beta
Articles 1.6.2-pl (getPage 1.2.3-pl, getResources to 1.5.0-pl, Quip 2.3.1-pl, Archivist 1.2.3-pl, taglister-1.1.7-pl).
PHP version: 5.3.8 and 5.3.14 LiteSpeed

No errors in the log.