Be clearer that innerHTML doesn't affect the scripting flag. (bug 6974) (whatwg r3176)

Be clearer that innerHTML doesn't affect the scripting flag. (bug 6974)
(whatwg r3176)
http://www.w3.org/Bugs/Public/show_bug.cgi?id=6974

Diffs for this change per section: 
http://people.w3.org/mike/diffs/html5/spec/Overview.1.2330.html#scripting-flag
http://people.w3.org/mike/diffs/html5/spec/Overview.1.2330.html#frameset-ok-flag

http://people.w3.org/mike/diffs/html5/spec/Overview.diff.html
http://dev.w3.org/cvsweb/html5/spec/Overview.html?r1=1.2329&r2=1.2330&f=h
http://html5.org/tools/web-apps-tracker?from=3175&to=3176

===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.2329
retrieving revision 1.2330
diff -u -d -r1.2329 -r1.2330
--- Overview.html 2 Jun 2009 02:57:06 -0000 1.2329
+++ Overview.html 2 Jun 2009 03:04:37 -0000 1.2330
@@ -53975,6 +53975,11 @@
   <code>Document</code> with which the parser is associated when the
   parser was created, and "disabled" otherwise.</p>
 
+  <p class="note">The <a href="#scripting-flag">scripting flag</a> can be enabled even
+  when the parser was originally created for the <a href="#html-fragment-parsing-algorithm">HTML fragment
+  parsing algorithm</a>, even though <code><a href="#script">script</a></code> elements
+  don't execute in that case.</p>
+
   <p>The <dfn id="frameset-ok-flag">frameset-ok flag</dfn> is set to "ok" when the parser is
   created. It is set to "not ok" after certain tokens are seen.</p>

Received on Tuesday, 2 June 2009 03:06:42 UTC