@mrboh I guess you have something like this?
We will fix this asap, but for now you can either go back to beta 3 or double encode your CDATA declarations (you can revert when we release the fix).
I'm wondering if a fix could be that we preserve CDATA sections that are inside a xhtml:script element?
Should we expect common use of CDATA in other situations that script?
<script>
<![CDATA[
function foo(a,b)
{
if (a < b && a > 0) then
{
return true;
}
else
{
return false;
}
}
]]>
</script>
I'm ashamed to admit I did not consider that obvious use case when changing CDATA behavior in beta 4. The new behavior is described here. We will fix this asap, but for now you can either go back to beta 3 or double encode your CDATA declarations (you can revert when we release the fix).
I'm wondering if a fix could be that we preserve CDATA sections that are inside a xhtml:script element?
Should we expect common use of CDATA in other situations that script?