Skip to content

Commit

Permalink
Clarify that UA should listen to focus change
Browse files Browse the repository at this point in the history
  • Loading branch information
youennf committed Mar 30, 2023
1 parent 04ede15 commit 3f69219
Showing 1 changed file with 8 additions and 3 deletions.
11 changes: 8 additions & 3 deletions index.html
Original file line number Diff line number Diff line change
Expand Up @@ -424,8 +424,13 @@ <h2>
</p>
</li>
<li>
<p>If the <a>current settings object</a>'s's [=relevant global object=]'s [=associated Document=]'s
[=top-level browsing context=] is losing <a data-cite="!HTML/#gains-focus">focus</a>,
<p>Let <var>topContext</var> be the <a>current settings object</a>'s's [=relevant global object=]'s
[=associated Document=]'s [=top-level browsing context=].</p>
</li>
<li>
<p>Start listening to <var>topContext</var>'s change of <a data-cite="!HTML/#gains-focus">focus</a>.
Whenever <var>topContext</var> is losing <a data-cite="!HTML/#gains-focus">focus</a>, stop listening
to <var>topContext</var>'s change of <a data-cite="!HTML/#gains-focus">focus</a> and
queue a global task on the <a data-cite="!HTML/#user-interaction-task-source">user interaction task source</a>
given <a>current settings object</a>'s [=relevant global object=] to run the following step:
<ol>
Expand All @@ -438,7 +443,7 @@ <h2>
This algorithm describes what to do for surface pickers implemented by the <a>user agent</a> but the same
requirement applies to surface pickers implemented outside of the <a>user agent</a>,
where the loss of capturing document focus is not necessarily the signal triggering setting
{{CaptureController/[[FocusChangeDisabled]]}} to<code>true</code>.
{{CaptureController/[[FocusChangeDisabled]]}} to <code>true</code>.
</p>
</li>
<li>
Expand Down

0 comments on commit 3f69219

Please sign in to comment.