From f458d159560d52392db32b435a9e09049afa443c Mon Sep 17 00:00:00 2001 From: Rakina Zata Amni Date: Wed, 19 May 2021 22:21:46 +0900 Subject: [PATCH 1/3] Add notes for focus & non-"fully active" documents Fixes #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 --- source | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/source b/source index 268cd4137f5..5bda2a54d09 100644 --- a/source +++ b/source @@ -73805,6 +73805,10 @@ END:VCARD area of the document. Which control is so designated changes over time, based on algorithms in this specification.

+

Even if a document is not fully active and not shown to the user, it + can still have a focused area of the document. If a document's fully + active state changed, its focused area of the document will stay the same.

+

The currently focused area of a top-level browsing context topLevelBC at any particular time is the focusable area-or-null returned by this algorithm:

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

+

The fully active state does not affect wheter an element is + being rendered or not. Even if a document is not fully active and not + shown at all to the user, elements within it can still qualify as "being rendered".

+

An element is said to intersect the viewport when it is being rendered and its associated CSS layout box intersects the viewport.

From ae32f6c63b6fc702f271e542633c3efadb8ef2f8 Mon Sep 17 00:00:00 2001 From: Rakina Zata Amni Date: Thu, 20 May 2021 17:38:31 +0900 Subject: [PATCH 2/3] Apply suggestions --- source | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/source b/source index 5bda2a54d09..fd9f5c236d1 100644 --- a/source +++ b/source @@ -73807,7 +73807,7 @@ END:VCARD

Even if a document is not fully active and not shown to the user, it can still have a focused area of the document. If a document's fully - active state changed, its focused area of the document will stay the same.

+ active state changes, its focused area of the document will stay the same.

The currently focused area of a top-level browsing context topLevelBC at any particular time is the focusable area-or-null returned by this algorithm:

@@ -113976,7 +113976,7 @@ console.assert(container.firstChild instanceof SuperP); means the element is not being rendered, though this might be overridden by the style sheets.

-

The fully active state does not affect wheter an element is +

The fully active state does not affect whether an element is being rendered or not. Even if a document is not fully active and not shown at all to the user, elements within it can still qualify as "being rendered".

From 89eedb67c36df5e5198b768a7eb487c638e0ccae Mon Sep 17 00:00:00 2001 From: Rakina Zata Amni Date: Fri, 21 May 2021 08:25:41 +0900 Subject: [PATCH 3/3] Add note for viewport --- source | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/source b/source index fd9f5c236d1..a591516da54 100644 --- a/source +++ b/source @@ -113983,6 +113983,12 @@ console.assert(container.firstChild instanceof SuperP);

An element is said to intersect the viewport when it is being rendered and its associated CSS layout box intersects the viewport.

+

Similar to the being rendered state, elements in non-fully + active documents can still intersect the viewport. The viewport + is not shared between documents and might not always be shown to the user, so an element in a + non-fully active document can still intersect the viewport associated + with its document.

+

This specification does not define the precise timing for when the intersection is tested, but it is suggested that the timing match that of the Intersection Observer API.