This is a page from the Cascading Style Sheets Working Group Blog. Some other places to find information are the “current work” page, the www-style mailing list, the Future of CSS syndicator, and the issue list on Github.
Do you want to know how the CSS WG works? Fantasai has written about:csswg, An Inside View of the CSS Working Group at W3C.
The CSS WG has published an updated Recommendation of the CSS Containment Module Level 1.
This CSS module describes the contain property, which indicates that the element’s subtree is independent of the rest of the page. This enables heavy optimizations by user agents when used well.
When a specification is published as a W3C Recommendation, it gives a indication of quality and stability: it has been extensively reviewed (including experts in accessibility, internationalization, security and privacy), reported issues have been addressed, tests have been written and passed by multiple implementations… But it doesn’t mean everything is perfect and flawless. Nothing really ever is.
After the fact, if we find typos, examples or notes whose phrasing can be improved, or other changes that do not impact the normative behavior specified, we can just make these changes. But for text that has an impact on the normative meaning of the specification, more care is needed. Starting with the 2020 revision of the W3C Process, we now have a fairly non intrusive way to work with such changes. The first step is to start by annotating, in the specification, what we would like to change and why. This lets us gather reviews on this provisional text and alert readers the official specification that something may be about to change, while preserving the original text as we wait for the new one to be ratified.
Later on, if and when these changes are confirmed to be the right thing to do, we can fold them in.
The CSS Containment Module Level 1 is the first W3C Recommendation to take advantage of this new process, and to include Candidate Corrections: one for a minor change that should make no difference to users but simplify implementations, and one for a fairly substantial rewrite of one section, which was found in retrospect to be insufficiently precise.
The CSS Working Group invites review of these two changes. More details about these changes and editorial ones can be found in the Changes section.
Please send feedback by either filing an issue in GitHub (preferable) or sending mail to the (archived) public mailing list www-style@w3.org with the spec code ([css-contain-1]
) and your comment topic in the subject line. (Alternatively, you can email one of the editors and ask them to forward your comment.)