Re: Cougar DTD: Do not use CDATA declared content for SCRIPT

David Perrell (davidp@earthlink.net)
Sat, 27 Jul 1996 17:05:17 -0700


Message-Id: <199607280013.RAA01723@iberia.it.earthlink.net>
From: "David Perrell" <davidp@earthlink.net>
To: "Ka-Ping Yee" <kpyee@aw.sgi.com>
Cc: <www-html@w3.org>
Subject: Re: Cougar DTD: Do not use CDATA declared content for SCRIPT
Date: Sat, 27 Jul 1996 17:05:17 -0700

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