Skip to content

Commit

Permalink
Add notes for focus & non-"fully active" documents
Browse files Browse the repository at this point in the history
Fixes whatwg#5878. Clarifies that the focused element stays the same/not reset when a document's "full active" state changed, and no events (focus/blur) are fired
  • Loading branch information
rakina committed May 19, 2021
1 parent 4cfb2b7 commit f458d15
Showing 1 changed file with 8 additions and 0 deletions.
8 changes: 8 additions & 0 deletions source
Original file line number Diff line number Diff line change
Expand Up @@ -73805,6 +73805,10 @@ END:VCARD</pre>
area of the document</dfn>. Which control is so designated changes over time, based on algorithms
in this specification.</p>

<p class="note">Even if a document is not <span>fully active</span> and not shown to the user, it
can still have a <span>focused area of the document</span>. If a document's <span>fully
active</span> state changed, its <span>focused area of the document</span> will stay the same.</p>

<p>The <dfn>currently focused area of a top-level browsing context</dfn> <var>topLevelBC</var> at
any particular time is the <span>focusable area</span>-or-null returned by this algorithm:</p>

Expand Down Expand Up @@ -113972,6 +113976,10 @@ console.assert(container.firstChild instanceof SuperP);
means the element is not <span>being rendered</span>, though this might be overridden by the style
sheets.</p>

<p class="note">The <span>fully active</span> state does not affect wheter an element is
<span>being rendered</span> or not. Even if a document is not <span>fully active</span> and not
shown at all to the user, elements within it can still qualify as "being rendered".</p>

<p>An element is said to <dfn>intersect the viewport</dfn> when it is <span>being rendered</span>
and its associated CSS layout box intersects the <span>viewport</span>.</p>

Expand Down

0 comments on commit f458d15

Please sign in to comment.