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 Working Group has published a Last Call Working Draft of CSS Cascading and Inheritance Level 3. This CSS module describes how to collate style rules and assign values to all properties on all elements by way of cascading (choosing a winning declaration among many) and inheritance (propagating values from parent to child). Notable additions since CSS2.1 include:
all shorthand to reset all CSS properties
initial and unset keywords to restore initial state
Significant changes since the last Working Draft are listed in the changes section and include changes to the all shorthand to exclude bidi controls and the replacement of the default keyword with unset (which has different semantics). (The draft also received an editorial overhaul.)
The deadline for comments is 26 August 2013. Please send comments to the (archived) public mailing list www-style@w3.org with the spec code ([css-cascade-3]) and your comment topic in the subject line. Alternatively, you can email one of the editors and ask them to forward your comment. If you need an extension, please request one before the deadline so we can accommodate.
The CSS Working Group has published an updated Working Draft of CSS Values and Units Level 3. This module describes the common values and units that CSS properties accept and the syntax used for describing them in CSS property definitions.
This update just clarifies a few minor points, including that CSS escaping syntax is interpreted when taking attribute values via attr(). All significant changes since the first CR are listed changes section.
As always, please send any feedback to the (archived) public mailing list www-style@w3.org with the spec code ([css3-values]) and your comment topic in the subject line. (Alternatively, you can email one of the editors and ask them to forward your comment.)
The CSS WG has published a Last Call Working Draft of CSS Counter Styles Level 3:
http://www.w3.org/TR/css-counter-styles-3/
This specification better defines the existing ‘list-style-type’ values that were introduced in CSS 2 and 2.1, and defines a few new styles for certain complex numbering systems that were not well served previously.
Additionally, it defines the @counter-style rule, which allows authors to define their own counter styles for use in ‘list-style-type’ and the “counter()” and “counters()” functions. The I18N Working Group is now maintaining a list of example counter styles for many of the world’s numbering systems at http://www.w3.org/International/docs/counter-styles/.
The CSSWG would appreciate feedback on this module, particularly on the aspects changed since the previous working draft:
Significant changes are listed at:
http://www.w3.org/TR/2013/WD-css-counter-styles-3-20130718/#changes
Please send any comments to the www-style mailing list and please, prefix the subject line with
var as shorthand to reset all custom properties.
default, introduce unset as “initial-or-inherit”
all shorthand does not reset direction, unicode-bidi, or var-*.
It’s been a long time coming but the CSS3 Fonts specification is now in the Last Call phase. The Last Call Working Draft was published last Thursday:
http://www.w3.org/TR/2013/WD-css-fonts-3-20130711/
The primary purpose of this module is to define and extend basic font selection properties (e.g. font-style, font-weight, font-stretch), support the use of downloadable fonts via the @font-face rule and allow the use of advanced font features available in modern font formats such as OpenType.
Changes since the previous published Feb 2013 Working Draft:
Please review the spec and post any comments or feedback you may have
to the www-style mailing list . The end of the Last Call period is
August 22.
text-underline-position: alphabetic.
em is computed font-size; ex, ch measure actual used value font metrics.
@font-feature-values object model dependency on missing WebIDL feature.
letter-spacing: <length> not disable inter-letter justification. See thread.
nav-* properties in spec, at risk in level 3.
! is invalid in Custom Properties (Variables).
elementsFromPoint() to CSSOM View spec.
@font-feature-values object model, with change from string to numbers.
@font-feature-values is an at-rule. (It is.)
font-feature-settings: none.
text-decoration set and font-variant non-normal, then we synthesize superscripts and subscripts, and text-decoration follows those metrics.
font-language-override feature to level 4.
text-underline-position: alphabetic and auto.
\[EOF] turns into U+FFFD except when inside a string, in which case it just gets dropped.
badstring and baduri make @supports rules invalid.
!important allowed in @supports
@charset handling and removing unused encodings. Conclusion to leave in issue and ask for feedback whether to add additional encoding patterns.
non-ascii is updated to include all non-ASCII chars.
UNICODE-RANGE token was discussed. No resolution recorded.
COMMA token.
NUMBER token (to include sign).
url() notations.
CDO/CDC were correctly fixed. No response was recorded in the minutes.
) ] }, badstring, badurl, top-level ; into variables
S+ instead of S*.)
attr() literally takes the attribute’s value without parsing; CSS escapes are not interpreted.
Browse by date:
Browse by category: