From 0fdf7eb669a48408fd2d248851bf0c7202f940f1 Mon Sep 17 00:00:00 2001
From: Tim Nguyen <nt1m@users.noreply.github.com>
Date: Fri, 5 Jan 2024 12:41:09 -0800
Subject: [PATCH] [css-view-transitions-1] Add a note to explain how the named
 elements are cleaned up (#9769)

---
 css-view-transitions-1/Overview.bs | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/css-view-transitions-1/Overview.bs b/css-view-transitions-1/Overview.bs
index 87c42ed6b5bf..061334f6c02a 100644
--- a/css-view-transitions-1/Overview.bs
+++ b/css-view-transitions-1/Overview.bs
@@ -1044,6 +1044,7 @@ urlPrefix: https://wicg.github.io/navigation-api/; type: interface;
 		: <dfn>named elements</dfn>
 		:: a [=/map=], whose keys are [=view transition names=] and whose values are [=captured elements=].
 			Initially a new [=map=].
+			Note: Since this is associated to the {{ViewTransition}}, it will be cleaned up when [=Clear view transition=] is called.
 
 		: <dfn>phase</dfn>
 		:: One of the following ordered phases, initially "`pending-capture`":
@@ -1949,6 +1950,7 @@ Changes from <a href="https://www.w3.org/TR/2023/WD-css-view-transitions-1-20230
 * Add a note about why 'view-transition-name' should be animatable.
 * `view-transition-name: auto` should be an invalid value. See <a href="https://github.com/w3c/csswg-drafts/issues/9639">issue 9639</a>.
 * Add note to explain paint order for entry animations. See <a href="https://github.com/w3c/csswg-drafts/issues/9672">issue 9672</a>.
+* Add note to explain how the named elements are cleaned up. See <a href="https://github.com/w3c/csswg-drafts/issues/9669">issue 9669</a>.
 
 <h3 id="changes-since-2022-05-25">
 Changes from <a href="https://www.w3.org/TR/2023/WD-css-view-transitions-1-20230525/">2022-05-25 Working Draft</a>