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.
Today we reviewed Last Call comments on CSS Speech:
voice-volume to volume-voice. (css3-speech issue-3)
play-during to CSS3 Speech; may consider for later level. (css3-speech issue-6)
voice-stress. (css3-speech issue-7)
voice-volume. (css3-speech issue-11)
silent value of voice-volume. (css3-speec issue-12)
speak and speak-as rejected, for reasons that they were split. (css3-speech issue-13)
<time> value restrictions to voice-duration to enforce good authoring practices. (css3-speech issue-14)
attr() as string, not implied.
vm unit or renaming it to vmin.
CSS is both a standard and a technology in development. Knowing which part of CSS is finished and which part you cannot use yet is a challenge. It’s been like that for more than a dozen years and is likely to stay that way for a couple more: the standard part is slowly growing, the part still in development has been growing as well, but should eventually diminish.
The CSS working group has written a document for implementers to explain the process of development and the current state of CSS. That document is called the CSS Snapshot. The working group intends to update it about every two years, or more often if needed.
But even if you are not an implementer, but only trying to follow the development of CSS and discuss it, e.g., on the <www-style@w3.org> mailing list, it may be useful to read the snapshot.
You can also read an alternative version, without the current state of CSS, but with a slightly expanded text describing the CSS process and its various types of documents.
Today W3C issued two new Recommendations: Selectors Level 3 and it dependency, CSS Namespaces. Selectors Level 3 has been a core part of CSS for awhile now, and is interoperably implemented by all modern browsers (including IE as of IE9). CSS Namespaces, which allows namespace-specific selectors, just completed its PR review phase, allowing both it and Selectors Level 3 to progress to W3C Recommendation.
Together with these publications, the CSSWG also issued a First Public Working Draft of Selectors Level 4. As explained in the CSS Snapshot, beyond level 2 CSS modules will level independently. Selectors is the first module to step up from Level 3 to Level 4. It collects together many of the proposals that were posted to www-style after the Selectors 3 feature freeze. (Note that pseudo-elements have been split out from this draft; they will reappear in other modules.) New features in Level 4 include:
:not() arguments to be a list of compound selectors rather than just a simple selector. E.g. :not(:hover:active,:focus:active)
:matches() as its “matches any” positive equivalent, allowing easier “or” operations. E.g. :matches(:focus, :hover)
:any-link as equivalent to :matches(:visited, :link). (Better name suggestions encouraged.)
:local-link to select local links (targetted at this document, or this domain, etc.)
:dir() pseudo-class to select based on element directionality (ltr vs rtl).
:current, :past, and :future to style time-dimensional displays.
:nth-match() and :nth-last-match() so you can write, e.g. :nth-match(odd of :not([hidden])).
label /for/ input.
$:any-link > img:only-child selects a link that contains a single image rather than a image that is the only elemental child of a link.
Keep in mind that Selectors 4 is a very early stage working draft, and the new features in it are much more at the brainstorming stage than the stable-go-implement stage. Some features may change drastically before CR; some may not make it through and be dropped. However, your feedback is welcome in shaping the draft going forward.
As always, please send feedback to www-style with the spec code ([css3-selectors], [css3-namespace], or [selectors4]) and your comment topic in the subject line. We will maintain errata for Selectors 3 and Namespaces; but, as with shipped software, active development will happen on the new mainline, Selectors 4.
:drag-over for CSS4-UI as :valid-drop-target.
column-span and margin collapsing againflex-flow proposal with logical values only.On 15 September 2011, the CSSWG officially published a new module: CSS Device Adaptation. This specification provides a way for an author to specify, in CSS, the size, zoom factor, and orientation of the viewport that is used as the base for the initial containing block. It is a CSS replacement for the proprietary HTML meta viewport tag.
As always, please send feedback to www-style with the spec code [css3-values] and your comment topic in the subject line.
On 6 September 2011, the CSSWG published an updated Working Draft of the CSS Values and Units Module Level 3. This module defines various new units as well as the calc(), attr(), and cycle() functional notations. With respect to the previous (2006!) draft, the cycle() notation is new. Other than that, not much has changed substantially. However the draft received a very major editorial overhaul, and has now be sync’ed to CSS2.1.
As always, send feedback to www-style with the spec code [css3-values] and your comment topic in the subject line. We’re especially asking for review on the functional notations, as their definitions are more complex than the other types.
On 1 September 2011, the CSSWG updated the official Working Drafts of CSS Writing Modes Level 3 and CSS Text Level 3, two modules dedicated to improving typesetting capabilities on the Web, particularly for non-European languages.
The main changes in Writing Modes were syntactic (renaming several properties and values) and fixing errors in the per-character vertical typesetting rules. A bidi box model error was fixed (corresponding errata will be issued for CSS2.1), and a text-combine-mode property was added to control tate-chu-yoko horizontal scaling. Feedback is encouraged on all aspects of the draft, but particularly on the vertical typesetting rules which probably still contain many errors.
The most significant change in the Text module was reworking the into a new text-spacing property. (Other changes are listed in the draft.) Feedback is especially requested on this aspect, and also on the newly-revised text-justify section (does it make sense yet?), and on text-emphasis-skip.
As always, send feedback to www-style with the spec code ([css3-writing-modes] or [css3-text]) and your comment topic in the subject line.
Browse by date:
Browse by category: