hixie: Explain noscript's non-xml support. (whatwg r6214)

hixie: Explain noscript's non-xml support. (whatwg r6214)

http://dev.w3.org/cvsweb/html5/spec/Overview.html?r1=1.4979&r2=1.4980&f=h
http://html5.org/tools/web-apps-tracker?from=6213&to=6214

===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.4979
retrieving revision 1.4980
diff -u -d -r1.4979 -r1.4980
--- Overview.html 10 Jun 2011 22:44:53 -0000 1.4979
+++ Overview.html 10 Jun 2011 22:48:26 -0000 1.4980
@@ -14020,9 +14020,12 @@
   historical reasons, the <code><a href="#the-noscript-element">noscript</a></code> element is handled
   differently by the <a href="#html-parser">HTML parser</a> based on whether <a href="#scripting-flag" title="scripting flag">scripting was enabled or not</a> when the
   parser was invoked.<p>The <code><a href="#the-noscript-element">noscript</a></code> element must not be used in <a href="#xml-documents">XML
-  documents</a>.<p class="note"><strong>The <code><a href="#the-noscript-element">noscript</a></code> element is only
-  effective in <a href="#syntax">the HTML syntax</a>, it has no effect in
-  <a href="#the-xhtml-syntax">the XHTML syntax</a>.</strong><div class="impl">
+  documents</a>.<p class="note">The <code><a href="#the-noscript-element">noscript</a></code> element is only effective
+  in <a href="#syntax">the HTML syntax</a>, it has no effect in <a href="#the-xhtml-syntax">the XHTML
+  syntax</a>. This is because the way it works is by essentially
+  "turning off" the parser when scripts are enabled, so that the
+  contents of the element are treated as pure text and not as real
+  elements. XML does not define a mechanism by which to do this.<div class="impl">
 
   <p>The <code><a href="#the-noscript-element">noscript</a></code> element has no other requirements. In
   particular, children of the <code><a href="#the-noscript-element">noscript</a></code> element are not

Received on Friday, 17 June 2011 09:53:20 UTC