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.
John Daggett from Mozilla took Microsoft’s marketing dept. to task for publishing PR articles using test results from unreviewed Microsoft tests “that wouldn’t even pass Microsoft’s internal review” while implying that they were accepted by W3C.
Advice for the future use of test results in marketing materials include:
jdaggett reviewed the font-variant-* features. Comments included:
font-variant-ligatures
should note that it doesn’t affect required ligatures.font-variant-alternates
in a way that does not tie the numbers to specific fonts, the problem being that the numbered options would be applied to fallback fonts, resulting in unexpected glyph selections. jdaggett protested that this isn’t a problem in reality while Adobe asserted that it will become more and more of a problem over time as use of advanced font technology increases. Several alternatives were proposed:
font-feature-settings
syntax by using idents and functional notation in place of strings. Bert noted that this may conflict with things like attr(), so the WG suggested prefixing each value with ot-
. Also discussed error-handling.font-language-override
‘s values are OT lang codes, not ISO lang codes. One suggestion was to accept ISO lang codes as idents and OT lang codes as strings.:ttb
solution, since it is supposedly a pseudo-class, but is selecting a property of the UA, not of the element. Media Queries are seen as a more appropriate place to detect features of the UA environment.Resolved: Add #rrggbbaa to CSS4 Color.
ointer-events
and overflow-x
/overflow-y
).::selection
: WG agrees with all of them; problem is now a matter of defining a model that accommodates all of them.Discussed request for list-style: auto: Authors can already map list styles to languages with :lang(), so this feature does not seem necessary. Also, it would require a great deal of research to specify adequately. The CSSWG would consider adding the feature described if someone else did the necessary research to draw up an exhaustive table mapping lang codes to list-style-types and the Internationalization Working Group approved it.
A new group at W3C is planning to draw up requirements for Indic layout, similar to the JLTF efforts.
Discussed Hyatt’s proposal
to alter syntax to make prefixing easier (which has the side effect of making the style sheet easier to understand, especially for someone unfamiliar with the Template module). The WG votes to add slot() notation to the ‘position’ values and to wrap the template strings in functional notation rather than add a new property as in Hyatt’s proposal.
Proposed to move CSS3 Values and Units to Candidate Recommendation to get calc() out. Starting by trimming any unfinished features and drawing up an at-risk list in prepartion for Last Call. This would mean: dropping fr
and gr
units, since they aren’t standalone units anyway; and marking vh
, vw
, vm
, and min()
and max()
at-risk.