- From: CVS User lsilli <cvsmail@w3.org>
- Date: Sat, 02 Nov 2013 05:41:02 +0000
- To: public-html-commits@w3.org
Update of /sources/public/html5/html-polyglot
In directory roscoe:/tmp/cvs-serv22732/html-polyglot
Modified Files:
html-polyglot.html
Log Message:
typo
--- /sources/public/html5/html-polyglot/html-polyglot.html 2013/11/02 05:38:57 1.8
+++ /sources/public/html5/html-polyglot/html-polyglot.html 2013/11/02 05:41:02 1.9
@@ -869,7 +869,7 @@
</section>
<section id="CDATA-comment-syntax-in-script">
<h6>Comment syntax in <code>script</code></h6>
- <p>Do not place strings in the shapes of the <code><script></code> start tag inside comments inside the <code>script</code> element as this causes the HTML parser, for compatibility related reasons, to <strong>not</strong> close the element on the next <code></script></code> end tag unless a closing <code>--></code> comment string has occurred first. Alternatively, if it doesn’t see any comment end first, the element will be closed on the <em>second</em> <code></script></code> end tag. This idiosyncratic behavior is not seen for the <code>style</code> element, however. </p>
+ <p>Do not place strings in the shape of the <code><script></code> start tag inside comments inside the <code>script</code> element as this causes the HTML parser, for compatibility related reasons, to <strong>not</strong> close the element on the next <code></script></code> end tag unless a closing <code>--></code> comment string has occurred first. Alternatively, if it doesn’t see any comment end first, the element will be closed on the <em>second</em> <code></script></code> end tag. This idiosyncratic behavior is not seen for the <code>style</code> element, however. </p>
<p class="note">To avoid these parsing suprises, including the differences between <code>style</code> and <code>script</code>, simply avoid comments in these elements.</p>
</section>
</section>
Received on Saturday, 2 November 2013 05:41:03 UTC