From 3f692199c9d84f4411e43a5e34c70abe0e10892f Mon Sep 17 00:00:00 2001 From: Youenn Fablet Date: Thu, 30 Mar 2023 09:01:54 +0200 Subject: [PATCH] Clarify that UA should listen to focus change --- index.html | 11 ++++++++--- 1 file changed, 8 insertions(+), 3 deletions(-) diff --git a/index.html b/index.html index 7d810a8..2e6ec4a 100644 --- a/index.html +++ b/index.html @@ -424,8 +424,13 @@

  • -

    If the current settings object's's [=relevant global object=]'s [=associated Document=]'s - [=top-level browsing context=] is losing focus, +

    Let topContext be the current settings object's's [=relevant global object=]'s + [=associated Document=]'s [=top-level browsing context=].

    +
  • +
  • +

    Start listening to topContext's change of focus. + Whenever topContext is losing focus, stop listening + to topContext's change of focus and queue a global task on the user interaction task source given current settings object's [=relevant global object=] to run the following step:

      @@ -438,7 +443,7 @@

      This algorithm describes what to do for surface pickers implemented by the user agent but the same requirement applies to surface pickers implemented outside of the user agent, where the loss of capturing document focus is not necessarily the signal triggering setting - {{CaptureController/[[FocusChangeDisabled]]}} totrue. + {{CaptureController/[[FocusChangeDisabled]]}} to true.