Editorial tweaks

Author: domenic

source

@@ -3757,6 +3757,12 @@ a.setAttribute('href', 'https://example.com/'); // change the content attribute
     <ul class="brief">
      <li><dfn data-x-href="https://drafts.csswg.org/css-pseudo/#file-selector-button-pseudo">'::file-selector-button'</dfn></li>
     </ul>
+
+    <p>The following term is defined in <cite>CSS Containment</cite>: <ref spec=CSSCONTAIN></p>
+
+    <ul class="brief">
+     <li><dfn data-x-href="https://drafts.csswg.org/css-contain/#skips-its-contents">skips its contents</dfn></li>
+    </ul>
    </dd>
 
 
@@ -57102,7 +57108,7 @@ interface <dfn>HTMLDetailsElement</dfn> : <span>HTMLElement</span> {
 
   <ol>
    <li>
-    <p>While <var>currentNode</var> has a parent node:</p>
+    <p>While <var>currentNode</var> has a parent node within the <span>flat tree</span>:</p>
 
     <ol>
      <li>
@@ -57114,14 +57120,14 @@ interface <dfn>HTMLDetailsElement</dfn> : <span>HTMLElement</span> {
        <var>currentNode</var> is slotted into.</p></li>
 
        <li><p>If the <code data-x="attr-details-open">open</code> attribute is not set on
-       <var>currentNode</var>, then <span data-x="concept-element-attributes-set-value">Set</span>
+       <var>currentNode</var>, then <span data-x="concept-element-attributes-set-value">set</span>
        the <code data-x="attr-details-open">open</code> attribute on <var>currentNode</var> to the
        empty string.</p></li>
       </ol>
      </li>
 
      <li><p>Otherwise, set <var>currentNode</var> to the parent node of
-     <var>currentNode</var> within the <span>flat tree</span>.</p></li>.
+     <var>currentNode</var> within the <span>flat tree</span>.</p></li>
     </ol>
    </li>
   </ol>
@@ -76169,14 +76175,20 @@ body { display:none }
   can navigate through the <span data-x="fip-matches">matches</span> by advancing the <span
   data-x="fip-active-match">active match</span> using the <span>find-in-page interface</span>.</p>
 
+  <p class="XXX"><a href="https://github.com/whatwg/html/issues/3539">Issue #3539</a> tracks
+  standardizing how <span>find-in-page</span> underlies the currently-unspecified <code
+  data-x="">window.find()</code> API.</p>
+
+  <h4>Interaction with <code>details</code></h4>
+
   <p>When find-in-page begins searching for matches, all <code>details</code> elements in the page
-  which do not have their <code data-x="attr-details-open">open</code> attribute set should have the
-  <a href="https://drafts.csswg.org/css-contain-2/#skips-its-contents">skipped contents</a> of their
-  second slot become accessible. without modifying the <code data-x="attr-details-open">open</code>
-  attribute in order to make find-in-page able to search through it. After find-in-page finishes
-  searching for matches, those <code>details</code> elements should have their contents become
-  skipped again. This entire process must happen synchronously (and so is not observable to users or
-  to author code).</p>
+  which do not have their <code data-x="attr-details-open">open</code> attribute set should have
+  the <span data-x="skips its contents">skipped contents</span> of their second slot become
+  accessible, without modifying the <code data-x="attr-details-open">open</code> attribute, in
+  order to make find-in-page able to search through it. After find-in-page finishes searching for
+  matches, those <code>details</code> elements should have their contents become skipped again.
+  This entire process must happen synchronously (and so is not observable to users or to author
+  code). <ref spec=CSSCONTAIN></p>
 
   <p>When find-in-page chooses a new <span data-x="fip-active-match">active match</span>, perform
   the following steps:</p>
@@ -76190,10 +76202,6 @@ body { display:none }
    revealing algorithm</span> on <var>node</var>.</p></li>
   </ol>
 
-  <p class="XXX"><a href="https://github.com/whatwg/html/issues/3539">Issue #3539</a> tracks
-  standardizing how <span>find-in-page</span> underlies the currently-unspecified <code
-  data-x="">window.find()</code> API.</p>
-
   <h4>Interaction with selection</h4>
 
   <p>The find-in-page process is invoked in the context of a document, and may have an effect on
@@ -115873,12 +115881,18 @@ details[open] > summary {
   expected to allow the user to request the details be shown or hidden.</p>
 
   <p>The <code>details</code> element's second <span data-x="concept-slot">slot</span> is expected
-  to have its <code data-x="attr-style">style</code> attribute set to "display:block;
-  content-visibility:hidden" when the <code>details</code> element does not have an <code
-  data-x="attr-details-open">open</code> attribute. When it does have the <code
+  to have its <code data-x="attr-style">style</code> attribute set to "<code data-x="">display:
+  block; content-visibility: hidden;</code>" when the <code>details</code> element does not have an
+  <code data-x="attr-details-open">open</code> attribute. When it does have the <code
   data-x="attr-details-open">open</code> attribute, the <code data-x="attr-style">style</code>
   attribute is expected to be removed from the second <span data-x="concept-slot">slot</span>.</p>
 
+  <p class="note">Because the slots are hidden inside a shadow tree, this <code
+  data-x="attr-style">style</code> attribute is not directly visible to author code. Its impacts,
+  however, are visible. Notably, the choice of <code data-x="">content-visibility: hidden</code>
+  instead of, e.g., <code data-x="">display: none</code>, impacts the results of various APIs that
+  query layout information.</p>
+
   <!-- https://mail.gnome.org/archives/usability/2006-June/msg00015.html -->
 
   </div>
@@ -123920,6 +123934,9 @@ INSERT INTERFACES HERE
    <dt id="refsCSSCASCADE">[CSSCASCADE]</dt>
    <dd><cite><a href="https://drafts.csswg.org/css-cascade/">CSS Cascading and Inheritance</a></cite>, E. Etemad, T. Atkins. W3C.</dd>
 
+   <dt id="refsCSSCONTAIN">[CSSCONTAIN]</dt>
+   <dd><cite><a href="https://drafts.csswg.org/css-contain/">CSS Containment</a></cite>, T. Atkins, F. Rivoal, V. Levin. W3C.</dd>
+
    <dt id="refsCSSCOLOR">[CSSCOLOR]</dt>
    <dd><cite><a href="https://drafts.csswg.org/css-color/">CSS Color Module</a></cite>, T. &Ccedil;elik, C. Lilley, L. Baron. W3C.</dd>