CSS WG Blog front page
Minor Update to CSS Values and Units Level 3
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 firstname.lastname@example.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.)
CSS Counter Styles 3 Last Call Working Draft Published
The CSS WG has published a Last Call Working Draft of CSS Counter Styles Level 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:
- technical feedback on any mistakes in the algorithms in the specs, or the predefined counter styles
- feedback on the new ‘pad’ and ‘speak-as’ descriptors
Significant changes are listed at:
Please send any comments to the www-style mailing list and please, prefix the subject line with
Minutes Telecon 2013-07-24
- Discussed botched Last Call publication of Variables, plan to republish soon, probably with additional issues resolved.
- Discussed use of
var as shorthand to reset all custom properties.
- Discussed plan for updating CSS2.1. Basically, need reviews of errata (to make sure they’re correct), testcases for each erratum, and implementation report proving we have passing implementations for each erratum.
- Resolved: Republish CSS3 Values and Units to update CR for minor fixes.
- Resolved: Drop
unset as “initial-or-inherit”
all shorthand does not reset
- Reviewed open Flexbox issues for discussion on the list / next week.
CSS3 Fonts Last Call Working Draft Published
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:
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:
- Moved font load events into a separate spec
- Tightened syntax rules for @font-feature-values rules
- Added grammar productions for @font-face and @font-feature-values rules
- Revised definition of ‘unicode-range’ descriptor
- Detailed font matching of composite faces
- Revised object model interface of CSSFontFeatureValuesRule
- Detailed effect of ‘font-size-adjust’ on relative unit sizes
- Reference the potentially CORS-enabled fetch method defined in HTML5
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
Minutes Telecon 2013-07-03
- Dirk requests review of CSSMatrix interface for publication as First Public Working Draft.
- Resolved: Tate-chu-yoko compression is UA-defined, however UAs MUST transform full-width chars/glyphs before compressing them. Spec will include John Daggett’s sample algorithm as an example for UAs to follow.
- Resolved: Text-decoration line thickness and position undefined in level 3. (Replaces previous resolution at Tokyo F2F.)
- Resolved: It is undefined in level 3 whether text and decorations are composited before shadowing or not.
- Resolved: Drop
- Resolved: Take CSS3 Text Decoration to Candidate Recommendation.
Minutes Telecon 2013-06-26
em is computed
ch measure actual used value font metrics.
- Resolved: Publish CSS3 Fonts as Last Call Working Draft after solving
@font-feature-values object model dependency on missing WebIDL feature.
- Discussed turning text-align into shorthand including text-align-last. (See proposal.) Rossen to collect data on existing usage to evaluate backwards-compatibility situation.
- Discussed having
letter-spacing: <length> not disable inter-letter justification. See thread.
Minutes Telecon 2013-06-19
- Resolved: Koji, fantasai and Jim Dovey as editors of CSS Ruby (which is now being rewritten)
- Resolved: Leave directional
nav-* properties in spec, at risk in level 3.
- Discussed errata’ing Media Queries 3
- Resolved: Top-level
! is invalid in Custom Properties (Variables).
- Resolved: Add
elementsFromPoint() to CSSOM View spec.
- Resolved: Multiple subject selectors allowed and all match (Selectors L4).
- Need review of Cross-Origin Style Sheets discussion.
Minutes Tokyo F2F June 2013 Part VI: Fonts, Text Decoration
- Resolved: Leave synthesis of italics in vertical text undefined.
- Resolved: Accept Tab’s proposal for
@font-feature-values object model, with change from string to numbers.
- Resolved: Discussed whether
@font-feature-values is an at-rule. (It is.)
- Resolved: We will use Promises in the font loading API.
- Resolved: We will not add Glenn’s proposal of
- Resolved: If an element has
text-decoration set and
font-variant non-normal, then we synthesize superscripts and subscripts, and text-decoration follows those metrics.
- Deferring any extensions to current
font-language-override feature to level 4.
Full minutes: Part I, Part II
- Resolved: Text decoration doesn’t consider descendant content for line thickness or positioning. (Note, this resolution was later superseded to make the behavior undefined.)
text-underline-position: alphabetic and
Minutes Tokyo F2F Part V: Core Syntax, Conditional Rules Syntax, Variables Syntax, Media Queries Syntax, Misc Syntax
Conditional Rules / Core Syntax
- Resolved: Whenever error-recovery closes open blocks, urls, strings, functions, brackets, etc., it implies the minimal tokens to close those constructs.
\[EOF] turns into
U+FFFD except when inside a string, in which case it just gets dropped.
- Resolved: Clarify that
@supports rules invalid.
!important allowed in
- Resolved: Publish CR with updates for CSS3 Conditional Rules.
@charset handling and removing unused encodings. Conclusion to leave in issue and ask for feedback whether to add additional encoding patterns.
- Resolved: Charset propagation from linking document is same-origin. Leave issue open until we’re more sure of this being stable.
- Resolved: NUL gets turned into replacement char U+FFFD.
- Confirmed that
non-ascii is updated to include all non-ASCII chars.
- Resolved: loosen the rules describing the way comments are serialized
- “Safe but pointless” change to
UNICODE-RANGE token was discussed. No resolution recorded.
- Reviewed addition of attribute-matching tokens for reducing lookahead.
- Reviewed addition of
- Reviewed change to
NUMBER token (to include sign).
- Reviewed change to bracket-matching of
- dbaron asked whether
CDC were correctly fixed. No response was recorded in the minutes.
- Resolved: Escaping in An+B notation falls out of tokenization rules. (Isn’t specialized for An+B.)
- Syntax is missing section that actually defines interpreting CSS syntax into style rules, at rules, etc.
- Resolved: Add Simon Sapin as co-editor.
Full minutes: Part I, Part II
- Resolved: Can’t put unmatched
; into variables
Media Queries and Misc
- Resolved: Media Aueries requires white space on both sides of a conjunction keyword.
- Resolved: Clarify in grammar that idents followed by open parenthesis must have white space between the two unless it’s a function. (I.e. use
S+ instead of
- Resolved: String and URL types for
attr() literally takes the attribute’s value without parsing; CSS escapes are not interpreted.
Minutes Tokyo F2F June 2013 Part IV: Priorities, Grid Layout, Alignment, Stacking Contexts, Backporting Policy
Philippe Le Hégaret, W3C’s Interaction Domain Leader, presented on the metrics W3C Management (W3M) has about the CSSWG’s progress over the past charter period. Discussed what was accomplished and whether that fits with the CSSWG’s own interests and priorities.
CSS Grid Layout
- Resolved: Snap-to-grid is out-of-scope for CSS Grid Layout module
- Discussed use of
position: grid to pull descendant elements up into an ancestor grid.
- Resolved: Absolute-positioning rules for grid items accepted as described in the spec, with
auto offsets meaning use padding edge of containing block.
- Resolved: Change issue 8 on sizing collapsed tracks into a more general issue about how to collapse a grid track.
- Plan to change
grid-template properties to
grid-template-[rows|columns|areas] and look into defining
grid-template as a shorthand for all three, using syntax similar to that in the Template module.
- Long discussion of default handling of grid container’s contents. Tentatively resolved on making
grid-auto-flow: row the default, which turns all grid container children into grid items and auto-flows them (similar to Flexbox). Issue still open for future discussion.
Tab and fantasai presented the new CSS Box Alignment draft, explaining changes in design and details since the earlier FPWD.
- Resolved: Need more work on baseline section; define first-line and last-line baseline for all things.
- Resolved: Table cells do create pseudo stacking-contexts (as resolved before) but borders and backgrounds (of the cell or its ancestors) are not in that pseudo stacking-context.
Principle: A change to a CSS3 spec that would make all CSS 2.1-compliant UAs incompliant needs to be backported to CSS2.1.
Note: If it would break content, we shouldn’t be making the change.
Browse by date:
Browse by category: