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 Anchor Positioning Module Level 1 has come a long way since its First Public Working Draft in 2023, with significant shifts to the syntax of the anchor()
function, the introduction of the position-area
property, the redesign of position-fallback
/@position-fallback
into the position-try
property and at-rule, the addition of anchor-scope
and position-visibility
, and many adjustments and improvements to the underlying algorithms, resulting in a more powerful and easier-to-use technology.
Special thanks go to Google, for spearheading the initial specification effort and working through multiple prototypes to identify and overcome technical hurdles; to Apple, for proposing and incorporating conceptual and interface changes and additions that brought this feature to the level of usability and system integration we expect for CSS; and to our creative Invited Expert Roman Komarov, who kept experimenting and pushing the edges of what was possible while reporting issues along the way, prompting myriad improvements to the feature. This kind of early engagement from authors on feature design paid off hugely in the development of CSS Grid Layout, and again here for CSS Anchor Positioning.
Our most recent Working Draft incorporates some relatively minor changes, showing that the draft is becoming increasingly stable, even as issues remain.
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-anchor-position-1]
) and your comment topic in the subject line. (Alternatively, you can email one of the editors and ask them to forward your comment.)
We are particularly interested in comments and suggestions on improving the accessibility guidance, and welcome examples of best practices that could be incorporated into the specification. Feel free to comment on issues (or file new ones) in the CSSWG repo, and note additional discussion in the WHATWG HTML repo and in the html-aam repo which you can contribute to.