Editorial: refactor innerText

Author: annevk

source

@@ -12272,12 +12272,11 @@ interface <dfn>DOMStringMap</dfn> {
   </div>
 
 
-  <h4>The <code data-x="dom-innerText">innerText</code> IDL attribute</h4>
+  <h4 id="the-innertext-idl-attribute">The <code data-x="dom-innerText">innerText</code> getter and
+  setter</h4>
 
   <dl class="domintro">
-
    <dt><var>element</var> . <code subdfn data-x="dom-innerText">innerText</code> [ = <var>value</var> ]</dt>
-
    <dd>
     <p>Returns the element's text content "as rendered".</p>
 
@@ -12287,16 +12286,15 @@ interface <dfn>DOMStringMap</dfn> {
 
   <div w-nodev>
 
-  <p>On getting, the <dfn><code data-x="dom-innerText">innerText</code></dfn> attribute must follow
-  these steps:</p>
+  <p>The <dfn><code data-x="dom-innerText">innerText</code></dfn> getter steps are:</p>
 
   <ol>
    <li>
-    <p>If this element is not <span>being rendered</span>, or if the user agent is a non-CSS user
-    agent, then return this element's <span>descendant text content</span>.</p>
+    <p>If <span>this</span> is not <span>being rendered</span> or if the user agent is a non-CSS
+    user agent, then return <span>this</span>'s <span>descendant text content</span>.</p>
 
     <p class="note">This step can produce surprising results, as when the <code
-    data-x="dom-innerText">innerText</code> attribute is accessed on an element not <span>being
+    data-x="dom-innerText">innerText</code> getter is invoked on an element not <span>being
     rendered</span>, its text contents are returned, but when accessed on an element that is
     <span>being rendered</span>, all of its children that are not <span>being rendered</span> have
     their text contents ignored.</p>
@@ -12305,7 +12303,7 @@ interface <dfn>DOMStringMap</dfn> {
    <li><p>Let <var>results</var> be a new empty <span>list</span>.</p></li>
 
    <li>
-    <p>For each child node <var>node</var> of this element:</p>
+    <p>For each child node <var>node</var> of <span>this</span>:</p>
 
     <ol>
      <li><p>Let <var>current</var> be the <span>list</span> resulting in running the <span>inner
@@ -12419,11 +12417,10 @@ interface <dfn>DOMStringMap</dfn> {
   stringifier and maybe expose it directly on <span data-x="concept-range">ranges</span>. See <a
   href="https://www.w3.org/Bugs/Public/show_bug.cgi?id=10583">Bugzilla bug 10583</a>.</p>
 
-  <p>On setting, the <code data-x="dom-innerText">innerText</code> attribute must follow these
-  steps:</p>
+  <p>The <code data-x="dom-innerText">innerText</code> setter steps are:</p>
 
   <ol>
-   <li><p>Let <var>document</var> be this element's <span>node document</span>.</p></li>
+   <li><p>Let <var>document</var> be <span>this</span>'s <span>node document</span>.</p></li>
 
    <li><p>Let <var>fragment</var> be a new <code>DocumentFragment</code> object whose <span>node
    document</span> is <var>document</var>.</p></li>
@@ -12469,7 +12466,7 @@ interface <dfn>DOMStringMap</dfn> {
    </li>
 
    <li><p><span data-x="concept-node-replace-all">Replace all</span> with <var>fragment</var> within
-   this element.</p></li>
+   <span>this</span>.</p></li>
   </ol>
 
   </div>
@@ -121894,8 +121891,8 @@ INSERT INTERFACES HERE
   href="https://www.w3.org/Consortium/Legal/2015/copyright-software-and-document">W3C Permissive
   Document License</a>.</p>
 
-  <p>Part of the revision history of the <code data-x="dom-innerText">innerText</code> IDL attribute
-  can be found in the <a
+  <p>Part of the revision history of the <code data-x="dom-innerText">innerText</code> getter and
+  setter can be found in the <a
   href="https://github.com/rocallahan/innerText-spec"><code>rocallahan/innerText-spec</code>
   repository</a>.</p>