Skip to content

Commit

Permalink
Reword a couple definitions and add a note
Browse files Browse the repository at this point in the history
  • Loading branch information
domfarolino committed Dec 17, 2024
1 parent 910492d commit 7fe3c3e
Showing 1 changed file with 17 additions and 13 deletions.
30 changes: 17 additions & 13 deletions source
Original file line number Diff line number Diff line change
Expand Up @@ -79853,16 +79853,20 @@ dictionary <dfn dictionary>ToggleEventInit</dfn> : <span>EventInit</span> {
the case with <span data-x="reading-flow-ordered focus navigation scope">reading-flow-ordered focus
navigation scopes</span>.</p>

<p>A <dfn>reading-flow-ordered focus navigation scope</dfn> is a <span>tabindex-ordered focus
navigation scope</span> whose <span>focus navigation scope owner</span> is a
<span>reading-flow-ordered scope owner</span>.</p>
<p class="note">The <span>tabindex value</span> rules do not give a precise ordering, as they are
composed mostly of "<!--non-normative-->should" statements and relative orderings.</p>

<p>The order within a <span>reading-flow-ordered focus navigation scope</span> is determined by
the <span>reading flow order</span> only. Each element's <span>tabindex value</span> is used to
determine whether the element is focusable, but it does not affect the order within the scope.</p>
<p>Every <span>reading-flow-ordered scope owner</span>'s <span>tabindex-ordered focus navigation
scope</span> is specifically a <dfn>reading-flow-ordered focus navigation scope</dfn>. The order
within a <span>reading-flow-ordered focus navigation scope</span> is determined by the
<span>reading flow order</span> algorithm; the use of <span>tabindex value</span> only determines
an item's focusability, but does not affect order within the scope.</p>

<p class="note">The rules there do not give a precise ordering, as they are composed mostly of
"<!--non-normative-->should" statements and relative orderings.</p>
<p class="note">The <span>tabindex-ordered focus navigation scope</span> of a <span>reading flow
item</span> — and any other <span>focus navigation scope owner</span> for that matter — is not
specifically a <span>reading-flow-ordered focus navigation scope</span>; it is a normal
<span>tabindex-ordered focus navigation scope</span> whose order is determined by <span>tabindex
value</span> as usual.</p>

<p>A <dfn>flattened tabindex-ordered focus navigation scope</dfn> is a list of <span
data-x="focusable area">focusable areas</span>. Every <span>focus navigation scope owner</span>
Expand Down Expand Up @@ -80092,7 +80096,7 @@ dictionary <dfn dictionary>ToggleEventInit</dfn> : <span>EventInit</span> {

<div w-nodev>

<h4>The reading flow</h4>
<h4>Reading flow</h4>

<p>A <dfn>reading-flow-ordered scope owner</dfn> is either: <ref>CSSDISPLAY</ref></p>

Expand Down Expand Up @@ -80142,10 +80146,10 @@ dictionary <dfn dictionary>ToggleEventInit</dfn> : <span>EventInit</span> {
<li><p><span>Break</span>.</p></li>
</ol>

<p class="note"> Different <var>item</var>s can have the same <span>inclusive ancestor</span>.
Only add to <var>output</var> if it is not already in the <span>reading flow order</span>. This
loop stops when the <span>inclusive ancestor</span> of <var>item</var> within the <span>flat
tree</span> is in the <var>scope</var>.</p>
<p class="note">Different <var>item</var>s can have the same <span>inclusive
ancestor</span>. Only add to <var>output</var> if it is not already in the <span>reading
flow order</span>. This loop stops when the <span>inclusive ancestor</span> of
<var>item</var> within the <span>flat tree</span> is in the <var>scope</var>.</p>
</li>

<li><p>Set <var>item</var> to the parent element of <var>item</var> within the <span>flat
Expand Down

0 comments on commit 7fe3c3e

Please sign in to comment.