QF: Javascript sections not XHTML compliant?
| From: | Ignatius Reilly | Date: | Wed, 22 Oct 2003 13:52:56 +0000 |
| Subject: | QF: Javascript sections not XHTML compliant? | ||
| Groups: | php.pear.dev | ||
| Request: | Send a blank email to pear-dev+get-22907@lists.php.net to get a copy of this message | ||
Sorry to be a bother again;
I just noticed that "hierselect" javascript sections generated by QF were
not XHTML-compliant
it is trivial to correct manually, but perhaps this raises a more general
question:
Should PEAR CS not require that JS sections - or for that matter all HTML
output - be XHTML-strict compliant? (didn't see anything to this effect in
the doc)
eg:
<script type="text/javascript">
//<![CDATA[
...
//]]>
</script>
instead of the usual
<script type="text/javascript">
<!--
...
// -->
</script>
which AFAI is not XHTML compliant
(Comments (<!-- ... -->) must not contain double dashes (--) )
therefore statements such as --x will cause non-conformance
Ignatius