@@ -1207,6 +1207,10 @@ Suppressing An Element's Contents Entirely: the 'content-visibility' property {#
12071207 and do not respond to hit-testing
12081208 (as if they had ''pointer-events: none'' ).
12091209
1210+ <wpt>
1211+ content-visibility/content-visibility-080.html
1212+ </wpt>
1213+
12101214 The user agent <em> should</em> additionally avoid as much layout/rendering work as possible
12111215 for [=skipped contents=] ;
12121216 the combination of heavy [=containment=]
@@ -1216,6 +1220,10 @@ Suppressing An Element's Contents Entirely: the 'content-visibility' property {#
12161220 the user-agent should retain the previously computed layout state if possible,
12171221 to allow the [=skipped contents=] to be displayed quickly at a later moment.
12181222
1223+ <wpt>
1224+ content-visibility/content-visibility-081.html
1225+ </wpt>
1226+
12191227 <div class=note>
12201228 If an element has a value other than ''content-visibility: visible'' ,
12211229 then the following properties hold:
@@ -1509,7 +1517,7 @@ Restrictions and Clarifications {#cv-notes}
15091517
15101518 Note: Thus, unlike the previous point,
15111519 the element <em> will</em> be correctly sized and aligned in the viewport.
1512- This is consistent with the order of the steps for the {{HTMLOrSVGElement /focus()}} method.
1520+ This is consistent with the order of the steps for the {{Window /focus()}} method.
15131521
151415227. If an <{iframe}> [=skips its contents=]
15151523 or is part of an element's [=skipped contents=] ,
0 commit comments