Skip to content

Commit

Permalink
Address comments
Browse files Browse the repository at this point in the history
  • Loading branch information
josepharhar committed May 11, 2021
1 parent 96b233d commit b2dc599
Showing 1 changed file with 13 additions and 11 deletions.
24 changes: 13 additions & 11 deletions source
Original file line number Diff line number Diff line change
Expand Up @@ -57105,8 +57105,9 @@ interface <dfn>HTMLDetailsElement</dfn> : <span>HTMLElement</span> {
<p>While <var>currentNode</var> has a parent node:</p>

<ol>
<li><p>If <var>currentNode</var> is slotted into the second slot of a <code>details</code>
element:</p>
<li>
<p>If <var>currentNode</var> is slotted into the second slot of a <code>details</code>
element:</p>

<ol>
<li><p>Set <var>currentNode</var> to the <code>details</code> element which
Expand Down Expand Up @@ -76168,22 +76169,23 @@ body { display:none }
data-x="fip-active-match">active match</span> using the <span>find-in-page interface</span>.</p>

<p>When find-in-page begins searching for matches, all <code>details</code> elements in the page
which are not <code data-x="attr-details-open">open</code> should have their second slot be added
to the rendering without modifying the <code data-x="attr-details-open">open</code> attribute.
After find-in-page finishes searching for matches, those <code>details</code> elements should have
their second slot be removed from the rendering again. This entire process must happen
which do not have their <code data-x="attr-details-open">open</code> attribute set should have
their second slot act as if it is added to the rendering 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 second slot be removed from the rendering again. This entire process must happen
synchronously (and so is not observable to users or to author code).</p>

<p>When find-in-page chooses a new <span data-x="fip-active-match">active match</span>, perform
the following steps:</p>

<ol>
<li><p>Let <var>node</var> be the first node in the <span data-x="fip-active-match">active
match</span>.</p></li>
<li><p>Let <var>node</var> be the first node in the <span data-x="fip-active-match">active
match</span>.</p></li>

<li><p><span>Queue a global task</span> on the <span>user interaction task source</span> given
<var>node</var>'s <span>relevant global object</span> to run the <span>ancestor details
revealing algorithm</span> on <var>node</var>.</p></li>
<li><p><span>Queue a global task</span> on the <span>user interaction task source</span> given
<var>node</var>'s <span>relevant global object</span> to run the <span>ancestor details
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
Expand Down

0 comments on commit b2dc599

Please sign in to comment.