[Bug 10901] Use same parsing for HTML <script> and SVG <script>

http://www.w3.org/Bugs/Public/show_bug.cgi?id=10901

--- Comment #2 from Adam Barth <w3c@adambarth.com> 2010-10-01 00:04:45 UTC ---
I don't have particularly strong feelings about this topic.  Eric might have a
stronger opinion because SVG is near and dear to his heart.

More generally, the more the tokenizer can be run without the tree builder, the
happier I am.  There are already some tokenization details that can't be done
correctly without a full tree builder, so that ship might have already sailed
anyway.

>From an implementation perspective, we're reasonably happy with the current
parsing algorithm.  There are very few angry users storming our bug database. 
Screwing around with something as delicate as tokenizing the script tag might
not be worth the risk without studying the risks carefully.  For example, the
following might be common:

<script>
// <![CDATA[
... JavaScript code ...
// OOPS!  I forgot the close the CDATA section
</script>
... HTML tags that are now getting swallowed into the script tag and case a
syntax error.  :(

For example, http://www.adambarth.com/ uses the "// <![CDATA[" talisman in the
script tags because I was trying to appease some XHTML validator.  Now, I think
I close the CDATA sections correctly, but that seems like an easy thing to
screw up.

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Friday, 1 October 2010 00:04:47 UTC