Subject: Re: [xsl] Understanding why <tag></tag> is the way it is (was Re: [xsl] IE Client side transformation issue) From: Abel Braaksma <abel.online@xxxxxxxxx> Date: Fri, 03 Aug 2007 19:06:16 +0200 |
This is rather interesting, because in XHTML <script> has become a PCDATA element.
yes because CDATA elements don't exist in XML.
Note however that this means that if you go
<script><![CDATA[some script]]></script>
then if the element is parsed as X(HT)ML the content of the element is "some script" so that is what the javascript sees. If on the other hand you send it as text/html then the content of the element is "<![CDATA[some script]]>" so that gets sent to javascript and generates javscript errors.
99 times out of 100 users blame this on IE not understanding <![CDATA but there is no CDATA section in the script element as < is not special within that scope. that is, it's user error, not a broken browser.
So people end up doing
<script> //<![CDATA[ some script //]]> </script>
so that the content of the element is
"// some script // " if parsed as XML and
" //<![CDATA[ some script //]]> "
if parsed as HTML, both being valid javascript (with comments)
Cheers, -- Abel Braaksma
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
Re: [xsl] Understanding why <tag></, David Carlisle | Thread | Re: [xsl] Understanding why <tag></, Abel Braaksma |
Re: [xsl] Understanding why <tag></, David Carlisle | Date | Re: [xsl] Understanding why <tag></, Manfred Staudinger |
Month |