From ecb375bf3c18da510a7bcf90f8ae776129e3af26 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Marcos=20C=C3=A1ceres?= <marcos@marcosc.com>
Date: Mon, 5 Dec 2022 15:56:24 +1100
Subject: [PATCH] Add page visibility change steps for Screen Orientation

See https://github.com/w3c/screen-orientation/pull/240 and https://github.com/w3c/screen-orientation/issues/219.

Part of #7396.
---
 source | 19 +++++++++++++++----
 1 file changed, 15 insertions(+), 4 deletions(-)

diff --git a/source b/source
index a9babb72feb..edbda3995b3 100644
--- a/source
+++ b/source
@@ -4288,6 +4288,15 @@ a.setAttribute('href', 'https://example.com/'); // change the content attribute
     </ul>
    </dd>
 
+   <dt>Screen Orientation</dt>
+   <dd>
+    <p>The following terms are defined in <cite>Screen Orientation</cite>: <ref spec=SCREENORIENTATION></p>
+
+    <ul>
+     <li><dfn data-x-href="https://w3c.github.io/screen-orientation/#dfn-screen-orientation-change-steps">screen orientation change steps</dfn></li>
+    </ul>
+   </dd>
+
    <dt>Storage</dt>
    <dd>
     <p>The following terms are defined in <cite>Storage</cite>: <ref spec=STORAGE></p>
@@ -75679,6 +75688,9 @@ END:VCARD</pre>
    <li><p>Set <var>document</var>'s <span>visibility state</span> to
    <var>visibilityState</var>.</p></li>
 
+   <li><p>Run the <span>screen orientation change steps</span> with <var>document</var>. <ref
+   spec=SCREENORIENTATION></p></li>
+
    <li>
     <p>Run any <dfn export>page visibility change steps</dfn> which may be defined in other
     specifications, with <span>visibility state</span> and <var>document</var>.</p>
@@ -75687,9 +75699,8 @@ END:VCARD</pre>
     from here into their specifications directly, instead of using the <span>page visibility change
     steps</span> hook, to ensure well-defined cross-specification call order. As of the time of
     this writing the following specifications are known to have <span>page visibility change
-    steps</span>, which will be run in an unspecified order: <cite>Device Posture API</cite>,
-    <cite>Screen Orientation API</cite>, and <cite>Web NFC</cite>. <ref spec=DEVICEPOSTURE> <ref
-    spec=SCREENORIENTATION> <ref spec=WEBNFC></p>
+    steps</span>, which will be run in an unspecified order: <cite>Device Posture API</cite>
+    and <cite>Web NFC</cite>. <ref spec=DEVICEPOSTURE> <ref spec=WEBNFC></p>
    </li>
 
    <li><p>Fire an event named <code data-x="event-visibilitychange">visibilitychange</code> at
@@ -131466,7 +131477,7 @@ INSERT INTERFACES HERE
    <dd><cite><a href="https://httpwg.org/specs/rfc8297.html">An HTTP Status Code for Indicating Hints</a></cite>, K. Oku. IETF.</dd>
 
    <dt id="refsSCREENORIENTATION">[SCREENORIENTATION]</dt>
-   <dd><cite><a href="https://w3c.github.io/screen-orientation/">Screen Orientation API</a></cite>, M. Lamouri, M. Cáceres. W3C.</dd>
+   <dd><cite><a href="https://w3c.github.io/screen-orientation/">Screen Orientation</a></cite>, M. Cáceres. W3C.</dd>
 
    <dt id="refsSCSU">[SCSU]</dt>
    <dd>(Non-normative) <cite><a href="https://www.unicode.org/reports/tr6/">UTR #6: A Standard Compression Scheme For Unicode</a></cite>, M. Wolf, K. Whistler, C. Wicksteed, M. Davis, A. Freytag, M. Scherer. Unicode Consortium.</dd>