From 9b0d0255467250426d11853c0d56e3d7e400d4a5 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Javier=20Fern=C3=A1ndez=20Garc=C3=ADa-Boente?=
 <jfernandez@igalia.com>
Date: Thu, 30 Nov 2023 00:32:24 +0100
Subject: [PATCH 1/3] Add 'onmove' Window event handler

---
 cssom-view-1/Overview.bs | 32 ++++++++++++++++++++++++++++++++
 1 file changed, 32 insertions(+)

diff --git a/cssom-view-1/Overview.bs b/cssom-view-1/Overview.bs
index 8d8e3cb3774..def0a61f651 100644
--- a/cssom-view-1/Overview.bs
+++ b/cssom-view-1/Overview.bs
@@ -1016,6 +1016,16 @@ compatibility reasons.
 
 Note: Some non-conforming implementations are known to return 32 instead of 24.
 
+<h2 id=extensions-to-the-windoweventhandlers-interface>Extensions to the {{WindowEventHandlers}} Interface</h3>
+
+<pre class=idl>
+partial interface WindowEventHandlers {
+    attribute EventHandler onmove;
+};
+</pre>
+
+<dfn attribute for=Window>onmove</dfn> is the <a>event handler IDL attribute</a> for the <a event>move</a> event.
+
 
 <h2 id=extensions-to-the-document-interface>Extensions to the {{Document}} Interface</h2>
 
@@ -1997,6 +2007,22 @@ Issue: In what order are scrollend events dispatched? Ordered based on scroll st
     1. Otherwise, <a>fire an event</a> named <a event>scrollend</a> at <var>target</var>.
 1. Empty <var>doc</var>'s <a>pending scrollend event targets</a>.
 
+<h3 id=moving-viewports>Moving viewports</h3>
+
+This section integrates with the <a for=/>event loop</a> defined in HTML. [[!HTML]]
+
+When <a for=/>updating the rendering</a>, after running the scroll steps:
+
+1. For each fully active Document in docs, <dfn export for=Document>run the move steps</dfn> for that Document.
+
+When asked to <a>run the move steps</a> for a {{Document}} <var>doc</var>, run these steps:
+
+1. If <var>doc</var>'s client window has had its position relative to the <a>Web-exposed screen area</a> changed
+    (e.g. as a result of the user moving the browser window)
+    since the last time these steps were run,
+    <a>fire an event</a> named <a event>move</a>
+    at the {{Window}} object associated with <var>doc</var>.
+
 <h3 id=event-summary>Event summary</h3>
 
 <i>This section is non-normative.</i>
@@ -2027,6 +2053,12 @@ Issue: In what order are scrollend events dispatched? Ordered based on scroll st
    <td>Fired at the {{VisualViewport}}, {{Document}}, or element when a scroll is <a lt="scroll completed">completed</a>: the
       {{VisualViewport}}, <a>viewport</a>, or element has been scrolled, the scroll sequence has ended and any scroll offset changes have
       been applied.
+  <tr>
+   <td><dfn event for="Window">move</dfn>
+   <td>{{Event}}
+   <td>{{Window}}
+   <td>Fired at the {{Window}} when the client window is moved relative to the <a>Web-exposed screen area</a>.
+  <tr>
 </table>
 
 

From d602ed949c31ac3038c1420f5ab513ff39c263a1 Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Tue, 26 Nov 2024 16:08:57 +0900
Subject: [PATCH 2/3] [cssomview] Swap the markup for definition and usage of
 "run the move steps"

---
 cssom-view-1/Overview.bs | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/cssom-view-1/Overview.bs b/cssom-view-1/Overview.bs
index def0a61f651..34a497002a6 100644
--- a/cssom-view-1/Overview.bs
+++ b/cssom-view-1/Overview.bs
@@ -2013,9 +2013,9 @@ This section integrates with the <a for=/>event loop</a> defined in HTML. [[!HTM
 
 When <a for=/>updating the rendering</a>, after running the scroll steps:
 
-1. For each fully active Document in docs, <dfn export for=Document>run the move steps</dfn> for that Document.
+1. For each fully active Document in docs, [=run the move steps=] for that Document.
 
-When asked to <a>run the move steps</a> for a {{Document}} <var>doc</var>, run these steps:
+When asked to <dfn export for=Document>run the move steps</dfn> for a {{Document}} <var>doc</var>, run these steps:
 
 1. If <var>doc</var>'s client window has had its position relative to the <a>Web-exposed screen area</a> changed
     (e.g. as a result of the user moving the browser window)

From aa2e8c8aed15a354add799abfc076fbf29b917be Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Tue, 26 Nov 2024 16:14:17 +0900
Subject: [PATCH 3/3] [cssom-view] Remove parts of move event defition that
 belong in HTML

---
 cssom-view-1/Overview.bs | 14 --------------
 1 file changed, 14 deletions(-)

diff --git a/cssom-view-1/Overview.bs b/cssom-view-1/Overview.bs
index 34a497002a6..eea210fb766 100644
--- a/cssom-view-1/Overview.bs
+++ b/cssom-view-1/Overview.bs
@@ -1016,16 +1016,6 @@ compatibility reasons.
 
 Note: Some non-conforming implementations are known to return 32 instead of 24.
 
-<h2 id=extensions-to-the-windoweventhandlers-interface>Extensions to the {{WindowEventHandlers}} Interface</h3>
-
-<pre class=idl>
-partial interface WindowEventHandlers {
-    attribute EventHandler onmove;
-};
-</pre>
-
-<dfn attribute for=Window>onmove</dfn> is the <a>event handler IDL attribute</a> for the <a event>move</a> event.
-
 
 <h2 id=extensions-to-the-document-interface>Extensions to the {{Document}} Interface</h2>
 
@@ -2011,10 +2001,6 @@ Issue: In what order are scrollend events dispatched? Ordered based on scroll st
 
 This section integrates with the <a for=/>event loop</a> defined in HTML. [[!HTML]]
 
-When <a for=/>updating the rendering</a>, after running the scroll steps:
-
-1. For each fully active Document in docs, [=run the move steps=] for that Document.
-
 When asked to <dfn export for=Document>run the move steps</dfn> for a {{Document}} <var>doc</var>, run these steps:
 
 1. If <var>doc</var>'s client window has had its position relative to the <a>Web-exposed screen area</a> changed