One thing I accomplished at this week's @w3ctag meeting in Wellington🇳🇿 was landing a PR to add the beginnings of a new section to our design principles document, on some principles behind the design of features on the Web: w3ctag.github.io/design-prin…
A @w3c CSS4 #CommunityGroup was recently launched to give more space for the discussion of what would a CSS4 label encompass - join if you want to help!
It is important to note that the @csswg decided not to try to describe #CSS for users and #developers. The group works primarily for implementors and hopes others like MDN would create resources for devs. For ex., check the CSS reference on @MozDevNet: developer.mozilla.org/en-US/…
That's why, starting from 1999, #CSS was decomposed into modules, each having its own life at its own pace. Each module defines a part of CSS to allow more immediate, incremental improvement of the specification: w3.org/Style/2011/CSS-proces…
All current #CSS specs have their own specific levels ranging from 1 to 5, but CSS as a whole does not have a version. Two reasons: 1) some features are easier to complete than others, 2) CSS became so big that it is too much work for the editors to maintain as a monolithic spec.
This specification was eventually renamed CSS 2.1 (a revision was published in June 2011 - Editors were Bert Bos, @viumlie, @Hixie and @t)
w3.org/TR/CSS2/
It's an opp. to clarify the land of #CSS levels... Of all CSS levels, CSS Level 2 (or CSS2) is the last monolithic level of CSS published as a @w3c#WebStandard, May 1998 - note the vintage look!: w3.org/TR/1998/REC-CSS2-1998…
These first CSS Level 5 modules come at a time of very active discussions on the value of numbered "versions" of #CSS - e.g. @ppk recently wrote "CSS4 is here!" quirksmode.org/blog/archives…
Media Queries Level 5 adds new media features to customize style sheets based on ambient light, environment blending, #JavaScript support and user preferences (e.g. color contrast); it also enables script-based custom media queries: w3.org/TR/2020/WD-mediaqueri…