You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: css-contain-2/Overview.bs
+2-2
Original file line number
Diff line number
Diff line change
@@ -1994,9 +1994,8 @@ Restrictions and Clarifications {#cv-notes}
1994
1994
must determine their proximity to the viewport
1995
1995
in the next [=update the rendering=] cycle.
1996
1996
The effect of this determination must be reflected in the visual update which results from this [=update the rendering=] cycle.
1997
+
See <a href="https://html.spec.whatwg.org/multipage/webappapis.html#event-loop-processing-model:content-visibility-auto">the event loop process model</a> for the concrete algorithm description.
1997
1998
1998
-
ISSUE: Reference the HTML spec algorithm here, when it's available.
1999
-
2000
1999
<div class=note>
2001
2000
When an element first gains ''content-visibility: auto'', it may or may not
2002
2001
be positioned on screen. The determination of this state and thus
@@ -2303,6 +2302,7 @@ This appendix is <em>informative</em>.
2303
2302
Changes from <a href="https://www.w3.org/TR/2022/WD-css-contain-2-20220917/">2022-09-17 Working Draft</a>
2304
2303
</h3>
2305
2304
2305
+
* Referenced the HTML event loop process model in the [[#cv-notes]], clarification 4.
2306
2306
* defined [=proximity to the viewport=] and used it in the [[#cv-notes]], clarification 4.
2307
2307
* 'content-visibility' applies to the same properties as [=size containment=] rather than [=layout containment=]
2308
2308
* clarified that 'content-visibility' affects the used value, not computed value, of the 'contain' property
0 commit comments