[html5] r5294 - [e] (0) Use a better name than 'write-neutralized'. Fixing http://www.w3.org/Bug [...]

whatwg at whatwg.org whatwg at whatwg.org
Mon Aug 16 12:07:24 PDT 2010


Author: ianh
Date: 2010-08-16 12:07:22 -0700 (Mon, 16 Aug 2010)
New Revision: 5294

Modified:
   complete.html
   index
   source
Log:
[e] (0) Use a better name than 'write-neutralized'.
Fixing http://www.w3.org/Bugs/Public/show_bug.cgi?id=10228

Modified: complete.html
===================================================================
--- complete.html	2010-08-16 18:27:45 UTC (rev 5293)
+++ complete.html	2010-08-16 19:07:22 UTC (rev 5294)
@@ -11415,7 +11415,7 @@
    <li>
 
     <p>If the <a href=#insertion-point>insertion point</a> is undefined and the
-    <code><a href=#document>Document</a></code> has the <a href=#write-neutralised>"write-neutralised"</a>
+    <code><a href=#document>Document</a></code> has the <a href=#ignore-destructive-writes>"ignore-destructive-writes"</a>
     flag set, then abort these steps.</p>
 
    </li>
@@ -13990,13 +13990,13 @@
   <a href=#parser-inserted>"parser-inserted"</a>, to let the parser know when to
   execute the script.</p>
 
-  <p>The fourth is a flag indicating whether or not the script block
-  is <dfn id=write-neutralised>"write-neutralised"</dfn>. Initially, <code><a href=#script>script</a></code>
-  elements must have this flag unset (script blocks, when created, are
-  not "write-neutralised"). This flag is used to ensure that scripts
-  <em>not</em> inserted by the parser but inserted while a parser is
-  active do not blow away the document if they use the <code title=dom-document-write><a href=#dom-document-write>document.write()</a></code>
-  API. <code><a href=#document>Document</a></code> objects can also have this flag set; it's
+  <p>The fourth is a flag is the <dfn id=ignore-destructive-writes>"ignore-destructive-writes"</dfn> flag.
+  Initially, <code><a href=#script>script</a></code> elements must have this flag unset
+  (script blocks, when created, do not have a "ignore-destructive-writes"
+  flag). This flag is used to ensure that scripts <em>not</em>
+  inserted by the parser but inserted while a parser is active do not
+  blow away the document if they use the <code title=dom-document-write><a href=#dom-document-write>document.write()</a></code> API.
+  <code><a href=#document>Document</a></code> objects can also have this flag set; it's
   propagated to the <code><a href=#document>Document</a></code> when the script runs.</p>
 
   <p>The fifth and sixth pieces of state are <dfn id="the-script-block's-type"><var>the script
@@ -14124,7 +14124,7 @@
     parser</a>, and the parser's <a href=#script-nesting-level>script nesting level</a>
     is non-zero, but this <code><a href=#script>script</a></code> element does not have
     the <a href=#parser-inserted>"parser-inserted"</a> flag set, the user agent must
-    set the element's <a href=#write-neutralised>"write-neutralised"</a> flag.</p>
+    set the element's <a href=#ignore-destructive-writes>"ignore-destructive-writes"</a> flag.</p>
 
    </li>
 
@@ -14371,10 +14371,10 @@
      <li>
 
       <p>If the <code><a href=#script>script</a></code> element's
-      <a href=#write-neutralised>"write-neutralised"</a> flag is set, then flag the
+      <a href=#ignore-destructive-writes>"ignore-destructive-writes"</a> flag is set, then flag the
       <code><a href=#document>Document</a></code> the <code><a href=#script>script</a></code> element was in
-      when the <a href=#write-neutralised>"write-neutralised"</a> flag was set as being
-      itself <a href=#write-neutralised>"write-neutralised"</a>. Let <var title="">neutralised doc</var> be that
+      when the <a href=#ignore-destructive-writes>"ignore-destructive-writes"</a> flag was set as being
+      itself <a href=#ignore-destructive-writes>"ignore-destructive-writes"</a>. Let <var title="">neutralized doc</var> be that
       <code><a href=#document>Document</a></code>.</p>
 
       <!-- theorem: this can only happen when the parser nesting
@@ -14399,7 +14399,7 @@
 
      <li>
 
-      <p>Remove the <a href=#write-neutralised>"write-neutralised"</a> flag from <var title="">neutralised doc</var>, if it was set in the earlier
+      <p>Remove the <a href=#ignore-destructive-writes>"ignore-destructive-writes"</a> flag from <var title="">neutralized doc</var>, if it was set in the earlier
       step.</p>
 
      </li>

Modified: index
===================================================================
--- index	2010-08-16 18:27:45 UTC (rev 5293)
+++ index	2010-08-16 19:07:22 UTC (rev 5294)
@@ -11339,7 +11339,7 @@
    <li>
 
     <p>If the <a href=#insertion-point>insertion point</a> is undefined and the
-    <code><a href=#document>Document</a></code> has the <a href=#write-neutralised>"write-neutralised"</a>
+    <code><a href=#document>Document</a></code> has the <a href=#ignore-destructive-writes>"ignore-destructive-writes"</a>
     flag set, then abort these steps.</p>
 
    </li>
@@ -13914,13 +13914,13 @@
   <a href=#parser-inserted>"parser-inserted"</a>, to let the parser know when to
   execute the script.</p>
 
-  <p>The fourth is a flag indicating whether or not the script block
-  is <dfn id=write-neutralised>"write-neutralised"</dfn>. Initially, <code><a href=#script>script</a></code>
-  elements must have this flag unset (script blocks, when created, are
-  not "write-neutralised"). This flag is used to ensure that scripts
-  <em>not</em> inserted by the parser but inserted while a parser is
-  active do not blow away the document if they use the <code title=dom-document-write><a href=#dom-document-write>document.write()</a></code>
-  API. <code><a href=#document>Document</a></code> objects can also have this flag set; it's
+  <p>The fourth is a flag is the <dfn id=ignore-destructive-writes>"ignore-destructive-writes"</dfn> flag.
+  Initially, <code><a href=#script>script</a></code> elements must have this flag unset
+  (script blocks, when created, do not have a "ignore-destructive-writes"
+  flag). This flag is used to ensure that scripts <em>not</em>
+  inserted by the parser but inserted while a parser is active do not
+  blow away the document if they use the <code title=dom-document-write><a href=#dom-document-write>document.write()</a></code> API.
+  <code><a href=#document>Document</a></code> objects can also have this flag set; it's
   propagated to the <code><a href=#document>Document</a></code> when the script runs.</p>
 
   <p>The fifth and sixth pieces of state are <dfn id="the-script-block's-type"><var>the script
@@ -14048,7 +14048,7 @@
     parser</a>, and the parser's <a href=#script-nesting-level>script nesting level</a>
     is non-zero, but this <code><a href=#script>script</a></code> element does not have
     the <a href=#parser-inserted>"parser-inserted"</a> flag set, the user agent must
-    set the element's <a href=#write-neutralised>"write-neutralised"</a> flag.</p>
+    set the element's <a href=#ignore-destructive-writes>"ignore-destructive-writes"</a> flag.</p>
 
    </li>
 
@@ -14295,10 +14295,10 @@
      <li>
 
       <p>If the <code><a href=#script>script</a></code> element's
-      <a href=#write-neutralised>"write-neutralised"</a> flag is set, then flag the
+      <a href=#ignore-destructive-writes>"ignore-destructive-writes"</a> flag is set, then flag the
       <code><a href=#document>Document</a></code> the <code><a href=#script>script</a></code> element was in
-      when the <a href=#write-neutralised>"write-neutralised"</a> flag was set as being
-      itself <a href=#write-neutralised>"write-neutralised"</a>. Let <var title="">neutralised doc</var> be that
+      when the <a href=#ignore-destructive-writes>"ignore-destructive-writes"</a> flag was set as being
+      itself <a href=#ignore-destructive-writes>"ignore-destructive-writes"</a>. Let <var title="">neutralized doc</var> be that
       <code><a href=#document>Document</a></code>.</p>
 
       <!-- theorem: this can only happen when the parser nesting
@@ -14323,7 +14323,7 @@
 
      <li>
 
-      <p>Remove the <a href=#write-neutralised>"write-neutralised"</a> flag from <var title="">neutralised doc</var>, if it was set in the earlier
+      <p>Remove the <a href=#ignore-destructive-writes>"ignore-destructive-writes"</a> flag from <var title="">neutralized doc</var>, if it was set in the earlier
       step.</p>
 
      </li>

Modified: source
===================================================================
--- source	2010-08-16 18:27:45 UTC (rev 5293)
+++ source	2010-08-16 19:07:22 UTC (rev 5294)
@@ -11755,7 +11755,7 @@
    <li>
 
     <p>If the <span>insertion point</span> is undefined and the
-    <code>Document</code> has the <span>"write-neutralised"</span>
+    <code>Document</code> has the <span>"ignore-destructive-writes"</span>
     flag set, then abort these steps.</p>
 
    </li>
@@ -14711,14 +14711,14 @@
   <span>"parser-inserted"</span>, to let the parser know when to
   execute the script.</p>
 
-  <p>The fourth is a flag indicating whether or not the script block
-  is <dfn>"write-neutralised"</dfn>. Initially, <code>script</code>
-  elements must have this flag unset (script blocks, when created, are
-  not "write-neutralised"). This flag is used to ensure that scripts
-  <em>not</em> inserted by the parser but inserted while a parser is
-  active do not blow away the document if they use the <code
-  title="dom-document-write">document.write()</code>
-  API. <code>Document</code> objects can also have this flag set; it's
+  <p>The fourth is a flag is the <dfn>"ignore-destructive-writes"</dfn> flag.
+  Initially, <code>script</code> elements must have this flag unset
+  (script blocks, when created, do not have a "ignore-destructive-writes"
+  flag). This flag is used to ensure that scripts <em>not</em>
+  inserted by the parser but inserted while a parser is active do not
+  blow away the document if they use the <code
+  title="dom-document-write">document.write()</code> API.
+  <code>Document</code> objects can also have this flag set; it's
   propagated to the <code>Document</code> when the script runs.</p>
 
   <p>The fifth and sixth pieces of state are <dfn><var>the script
@@ -14884,7 +14884,7 @@
     parser</span>, and the parser's <span>script nesting level</span>
     is non-zero, but this <code>script</code> element does not have
     the <span>"parser-inserted"</span> flag set, the user agent must
-    set the element's <span>"write-neutralised"</span> flag.</p>
+    set the element's <span>"ignore-destructive-writes"</span> flag.</p>
 
    </li>
 
@@ -15164,11 +15164,11 @@
      <li>
 
       <p>If the <code>script</code> element's
-      <span>"write-neutralised"</span> flag is set, then flag the
+      <span>"ignore-destructive-writes"</span> flag is set, then flag the
       <code>Document</code> the <code>script</code> element was in
-      when the <span>"write-neutralised"</span> flag was set as being
-      itself <span>"write-neutralised"</span>. Let <var
-      title="">neutralised doc</var> be that
+      when the <span>"ignore-destructive-writes"</span> flag was set as being
+      itself <span>"ignore-destructive-writes"</span>. Let <var
+      title="">neutralized doc</var> be that
       <code>Document</code>.</p>
 
       <!-- theorem: this can only happen when the parser nesting
@@ -15193,8 +15193,8 @@
 
      <li>
 
-      <p>Remove the <span>"write-neutralised"</span> flag from <var
-      title="">neutralised doc</var>, if it was set in the earlier
+      <p>Remove the <span>"ignore-destructive-writes"</span> flag from <var
+      title="">neutralized doc</var>, if it was set in the earlier
       step.</p>
 
      </li>




More information about the Commit-Watchers mailing list