(unknown charset) Re: Cougar DTD: Do not use CDATA declared content for SCRIPT

Ping :

Can the CDATA content definition be changed to accommodate the
treatment of content as an implicitly marked section? Whether it's a
parsing nightmare must be debatable, since both NSN v2 and MSIE v3b2
apparently treat SCRIPT content as such, excepting an initial comment
start.

You consider the options from a practical point of view. A practical
point of view would include the option already implemented:
 
What's the likelihood of finding "</script>" in a script?
    Let's just say, as is the case now, that it can't be there.

My problem with the explicitly marked section thing is that the
<script></script> pair already marks an element with a particular type
of content. Additional markup is redundant.

David Perrell

Received on Saturday, 27 July 1996 20:14:16 UTC