Closed
Bug 1763647
Opened 2 years ago
Closed 2 years ago
content-visibility: hidden and content-visibility: auto should enable containment
Categories
(Core :: Layout, enhancement)
Core
Layout
Tracking
()
RESOLVED
FIXED
101 Branch
Tracking | Status | |
---|---|---|
firefox101 | --- | fixed |
People
(Reporter: mrobinson, Assigned: mrobinson)
References
Details
Attachments
(1 file)
The specification (https://drafts.csswg.org/css-contain/#content-visibility) says:
If an element has a value other than content-visibility: visible, then the following properties hold:
- layout containment ensures that the user-agent is able to omit layout work in skipped subtrees, since the results of such layouts will not affect elements outside of the container element.
- style containment ensures that counters do not have to be processed in skipped subtrees, since they do not affect counters outside of the container element.
- paint containment ensures that ink overflow of painted contents is clipped; this, in turn, means that user-agent can reliably determine when the visible portion of the element approaches the viewport (and, for content-visibility: auto, start painting it).
- size containment ensures that the user-agent is able to omit layout in skipped subtrees, since the results of such layouts will not affect the container element’s size.
Note that in the content-visibility: auto case, layout containment, style containment, and paint containment persist even if the element is not skipped. This is done to prevent layout changes that would be incurred by containment changes as a result of an element entering and exiting the skipped state.
This bug tracks turning on containment based on the content-visibility
property.
Assignee | ||
Comment 1•2 years ago
|
||
Updated•2 years ago
|
Assignee: nobody → mrobinson
Status: NEW → ASSIGNED
Pushed by ealvarez@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/177edcaff970 content-visibility: hidden and content-visibility: auto should enable containment r=emilio
Comment 3•2 years ago
|
||
bugherder |
Status: ASSIGNED → RESOLVED
Closed: 2 years ago
status-firefox101:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 101 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•