From 72a193ff84a7b23085c00da000ffe0ad0c00b20f Mon Sep 17 00:00:00 2001
From: Helmut Januschka <helmut@januschka.com>
Date: Wed, 27 May 2026 22:25:11 +0200
Subject: [PATCH] Preserve focused area across bfcache reactivation

Promotes the existing note's preservation statement to normative prose
and clarifies that no focus or blur events fire as a side effect of a
Document moving into or out of the back/forward cache. This aligns the
spec text with the implementer agreement reached in #5878.

Closes: #12496
---
 source | 11 +++++++++--
 1 file changed, 9 insertions(+), 2 deletions(-)

diff --git a/source b/source
index 2825d4d2f50..4737f2ba49c 100644
--- a/source
+++ b/source
@@ -85851,8 +85851,15 @@ dictionary <dfn dictionary>CommandEventInit</dfn> : <span>EventInit</span> {
   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 changes, its <span>focused area of the document</span> will stay the same.</p>
+  can still have a <span>focused area of the document</span>.</p>
+
+  <p>A document's <span>focused area of the document</span> does not change as a side effect of
+  the document's <span>fully active</span> state changing. In particular, neither storing the
+  document in the <a href="#note-bfcache">back/forward cache</a> nor <span data-x="reactivate a
+  document">reactivating</span> it from the <a href="#note-bfcache">back/forward cache</a>
+  affects its <span>focused area of the document</span>, and as a result no <code
+  data-x="event-focus">focus</code> or <code data-x="event-blur">blur</code> events are fired
+  on account of those transitions.</p>
 
   <div algorithm>
   <p id="currently-focused-area-of-a-top-level-browsing-context">The <dfn>currently focused area of