[css-view-transition-1][editorial] Change visibility: hidden analogy to opacity: 0 (#13378)

* [css-view-transition-1][editorial] Change `visibility: hidden` analogy to `opacity: 0`

Author: sb3nder

css-view-transitions-1/Overview.bs

@@ -837,7 +837,7 @@ urlPrefix: https://wicg.github.io/navigation-api/; type: interface;
 	the boxes generated by any element in that {{Document}} with [=captured in a view transition=]
 	and its [=element contents=],
 	except [=ViewTransition/transition root pseudo-element=]'s [=tree/inclusive descendants=],
-	are not painted (as if they had ''visibility: hidden'') and
+	are not painted (as if they had ''opacity: 0'') and
 	do not respond to hit-testing (as if they had ''pointer-events: none'').
 
 	Note: Elements participating in a transition need to skip painting in their DOM location because
@@ -2000,6 +2000,7 @@ This appendix is <em>informative</em>.
 <h3 id="changes-since-2024-03-28">
 Changes from <a href="https://www.w3.org/TR/2024/CRD-css-view-transitions-1-20240328/">2024-03-28 Candidate Recommendation Draft</a>
 </h3>
+* Update wording to use `opacity: 0` instead of `visibility: hidden`. See <a href="https://github.com/w3c/csswg-drafts/issues/12629">issue 12629</a>.
 * Always flush the queue of update callbacks before capturing the old state. See <a href="https://github.com/w3c/csswg-drafts/issues/11292">issue 11922</a>.
 * Disallow <css>match-element</css> as a custom-ident. See <a href="https://github.com/w3c/csswg-drafts/issues/10995">Issue 10995</a>.
 * Add a non-normative note to explain that ''::view-transition-image-pair()'' would typically not need custom styling. See <a href="https://github.com/w3c/csswg-drafts/issues/11926#issuecomment-2916977161">issue 11926</a>