From c66c9f54a24c0ed589f48f4d1852b230f019c6da Mon Sep 17 00:00:00 2001
From: Khushal Sagar <khushalsagar@chromium.org>
Date: Fri, 7 Oct 2022 15:29:32 -0400
Subject: [PATCH] Add spec text for rendering suppression during transition

---
 source | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/source b/source
index 6bad8a47add..a750e835640 100644
--- a/source
+++ b/source
@@ -96627,11 +96627,13 @@ import "https://example.com/foo/../module2.mjs";</code></pre>
       reasons, but considering content presentable even if it's outside the viewport.</p>
 
       <p>A <span>browsing context</span> has no <span data-x="rendering opportunity">rendering
-      opportunities</span> if its <span>active document</span> is <span>render-blocked</span>;
+      opportunities</span> if its <span>active document</span> is <span>render-blocked</span>
+      or its <span>active document</span>'s has <span>transition suppressing rendering</span>;
       otherwise, <span data-x="rendering opportunity">rendering opportunities</span> are determined
       based on hardware constraints such as display refresh rates and other factors such as page
       performance or whether the document's <span>visibility state</span> is "<code
-      data-x="">visible</code>". Rendering opportunities typically occur at regular intervals.</p>
+      data-x="">visible</code>". Rendering opportunities typically occur at regular intervals.
+      <ref spec=CSSVIEWTRANSITIONS></p>
 
       <p class="note">This specification does not mandate any particular model for selecting
       rendering opportunities. But for example, if the browser is attempting to achieve a 60Hz