CSS WG Blog front page
CSS Cascade Level 3 Candidate Recommendation
The CSSWG recently published CSS Cascading and Inheritance Level 3 as a Candidate Recommendation. W3C encourages implementations of this module, and welcomes feedback resulting from such implementation. Requests for new features will be assigned to Level 4.
CSS Cascading and Inheritance Level 3 describes how to collate style rules and, by way of cascading an inheritance, assign values to all properties on all elements in the document. New features since the previous level (CSS2.1) include:
The spec also collapses all inputs to the cascade into a single list, making it easier to understand how different levels appended to the CSS2.1 definitions fit together.
Significant changes since the Last Call Working Draft are listed changes section.
As always, please send feedback to the (archived) public mailing list www-style@w3.org with the spec code ([css-cascade]) and your comment topic in the subject line. (Alternatively, you can email one of the editors and ask them to forward your comment.)
Minutes Telecon 2013-10-02
- Resolved: Publish a new working draft of Generated Content for Paged Media (GCPM).
- Page Floats will be discussed later when Hakon is on the call.
- Resolved: Krit and Rik will be co-editors for DOMMatrix, DOMPoint and DOMPointLiteral
- Decision to publish a new editor’s draft for DOMMatrix, DOMPoint and DOMPointLiteral taken to e-mail on W3C-CSS-WG mailing-list after misunderstanding and invalid decision during call given the request. Correction made by co-chair Daniel (glazou) after end of the call.
- All but one issue has been addressed for Shapes. Astearns requested another week to work through the syntax issues on the remaining issue.
- The different ways that various specs point to elements were discussed. Some testing will be run to see what method current implementations are using in order to determine how to proceed.
- The group expressed an interest to have a few hours meeting with the SVG WG during the Wednesday of the January F2F in Seattle.
- Glazou will talk to Bert further about finding out if the WG will meet on the Sunday of the November F2F.
Full minutes
Minutes Paris F2F Sept. 2013 Part III: Masking, Display Tree or DOM, Flexbox, Color Module, Charter, Ruby, Text, Writing Modes, Animations
CSS Masking – Review Request
- Resolved: The WG will review Masking LC transition on the 10/9 telcon
Full Minutes
Spec Referenced
Any interest in working out selection/editing based on display tree rather than DOM?
- Though some interest was expressed, it was deemed currently not enough to proceed to an ED
Full Minutes
Flexbox
- Resolved: Use 2-pass algorithm to resolve % height children of flex stretched items pending dholbert’s feedback.
- Resolved: Proposed issue-1 edits are approved.
Full Minutes
Spec Referenced
Color Module
- Resolved: Add ChrisL as co-editor on CSS4 color
- Resolved: Pull in SVG2 color section into CSS4 color
- Resolved::
rgb() and rgba() will accent number rather than integer
- Resolved: Allow
angle in place of number for hues
- Resolved: Accept
percentage as alpha-value
- Resolved: Accept rgba hex colors
- Resolved: No change to number of arguments to rgb/hsl
- Resolved: Add
color-correction property to CSS4 color draft, with issue about the problem it’s trying to solve and consideration that it might not be the right solution.
Full Minutes
Spec Referenced
Charter
- There was discussion about how to handle timelines for specs as a part of the rechartering process.
- The group also discussed possible alterations and alternatives to the current charter model that may better fit the process of the WG.
- It was decided that the chairs, plinss and glazou, would draw up a list of priorities from existing WG documentation and submit it to the WG for review and approval before inclusion in the charter documentation.
Full minutes
CSS Ruby
- The new proposal for CSS Ruby was discussed section by section. The WG had several questions and concerns about most sections, but decided to move to Working Draft after fantasai added some text clarifying the intention of the
auto keyword.
- Resolved: Publish fantasai’s CSS Ruby draft as a Working Draft.
Full Minutes
Spec Referenced
CSS Text
- Resolved:
letter-spacing: length doesn’t restrict justification. text-justify:inter-word; disables inter-letter justification.
- Resolved:
letter-spacing:normal; computes to 0.
- Resolved: Spec the dependence of
text-align-last on text-align:justify and mark issue for feedback on shorthanding vs. not.
- Resolved: Drop minimum/optimum/maximum values for word-spacing.
- Resolved: Keep
text-align: start end in, add an issue about naming, and mark it at risk.
- Resolved: Take css3-text to last call pending resolving issues from jdaggett.
Full Minutes
Spec Referenced
Writing Modes
- Koji found a difficulty from the decisions made regarding
tcy and writing modes yesterday.
- Resolved: Drop digits 1
- Resolved: css3-writing-modes to Last Call when edits agreed in this meeting are completed.
Full Minutes
Spec Referenced
Animations
- dbaron brought the group up to speed on the changes he had made to the spec.
- The order in which events will fire and boundary points were of particular concern, but it was decided that an e-mail conversation and testing were the best way to answer the outstanding questions.
Full Minutes
Spec Referenced
Minutes Paris F2F Sept. 2013 Part II: Font Load Events, TPAC & F2F Schedule, Masking, Naming of DOMPoint Quad and Matrix, Sticky Position, Text-Combing Naming, GCPM, Writing Modes, Compositing Spec
Font Load Events
- Discussed possible new spec for font load events, including improvements on the explanatory text and security concerns about
match() function.
FontFace interface issues were also discussed. TabAtkins requested that others review the spec to allow for implementation to occur.
Full Minutes
Spec Discussed
TPAC and F2F Scheduling
- Still looking for a space for a Sunday meeting at Shenzhen in November.
- Tentative resolution for Jan 27-31, joint meeting with SVG, in Seattle, hosted by Adobe.
- Investigating Asian locations for week of May 12-16.
- Sophia some time in September.
Full Minutes
CSS Masking
- Resolved: The
mask-image property only takes one layer.
- Resolved: Combine CSS Images and CSS Mask references in the SVG mask references.
- Resolved: Default value for
mask-repeat is no-repeat.
- Resolved: Add keyword
none to mask.
- Resolved: Default for
mask-position is center.
- Resolved: Default for
mask-origin is border-box.
Full Minutes
Spec Referenced
Naming of DOMPoint, Quad, and Matrix
- Resolved: Provisionally go for DOM prefix.
Full Minutes
Sticky Position
- The group agreed that
Sticky would add good functionality.
- Rossen will add text about
Sticky to the Position module.
- Resolved: add Rossen as editor to Position module.
Full Minutes
Spec Referenced
Text-Combine Naming
- Options for
Text-Combine name was discussed, but no solution was decided.
- Ideas floated include
text-combine-horizontal, glyph-orientation-horizontal, text-combine, and text-combine-upright.
Full Minutes
GCPM
- Resolved: Publish sections 1-5, 7, and 13 of GCPM ED as a new working draft.
- Resolved: Move section 6 to CSS3 Page; section 8 to CSS Color; section 9 to CSS3 Page; sections 10, 11, 14 to Overflow; section 12 to Page Floats (new spec); section 14 to Overflow (for now, Pseudo-Elements when we write it); section 15 removed; sections 16 and 17 to Page Floats.
Full Minutes
Specs Referenced: GCPM, Page Floats, CSS3 Page, CSS Color, and Overflow
CSS Writing Modes
- Various options were discussed to address the inheritance of
text-combine-horizontal. The group came to three options, but decided to continue the conversation later to decide between those choices.
- Koji will update the spec to UTR50
- Rossen check if it’s ok to drop support for
text-combine-horizontal: digits 1
Full Minutes
Spec Referenced
Issue 2 in Compositing Spec
- Resolved: Close issue #2
- Resolved: Everyone review Compositing/Blending, we’ll take up the question of Last Call publication at next telcon.
Full Minutes
Spec Referenced
Minutes Paris F2F Sep. 2013 Part I- Grid Layout, Style Attributes, Spec Preprocessor, CSSOM, Image Values, Multi Column Layout, Shapes & Regions, Transforms
Grid Layout
- Resolved: Formally accept renaming
grid-definition-rows/grid-definition-columns/grid-template to grid-template-rows/grid-template-columns/grid-template-areas.
- Resolved: Grid child static position is resolved as if it’s the sole child. The definition will also be copied over to Flexbox.
- Resolved: Add more examples to the absolute position grid items section.
- Resolved: Named areas create implicitly named lines.
- Resolved: Make named areas just desugar into named lines.
- Resolved: Leave subgrids in level 1, mark it and its component parts individually as at-risk.
- Resolved:
getComputedStyle returns used values for grid-template-rows/columns.
- Resolved: Don’t change
grid-area to grid-field.
Full Minutes
Spec Discussed
Style Attributes
- Resolved: Take Style Attribute to Proposed Recommendation, with explanation of
xml:base interaction test failure as an xml:base bug.
Full Minutes
Spec Discussed
Spec Preprocessor
Tab presented his new spec preprocessor, Bikeshed.
Full Minutes
CSSOM
- Resolved:
setProperty‘s handling of importance logically behaves same as appending a declaration (like IE/WebKit).
- Resolved: Add a
setPropertyValue and setPropertyPriority application programming interfaces.
Full Minutes
Spec Discussed
CSS Image Values
- Resolved: When transitioning from plain image A to
foo(A), infer the foo() on the other side (using no-op arguments).
- Resolved: Mark as open issue whether interpolating complex images with the same source (e.g.
foo(A) to bar(A)) uses recursive interpolation (building a stack of compatible functions, e.g. foo(bar(A))) or just uses cross-fade().
- Resolved: Accept proposal to shift misordered gradient stop fixup rules to after missing position interpolation and transition interpolation in order to make transitions layout-independent.
- Resolved: No magic length interpolation for angle transitions in
linear-gradient().
- Resolved: Cannot interpolate to/from gradients with keyword direction unless using the same keyword.
Full Minutes
Spec Discussed
Multi-Column Layout
- Resolved: Discussed layering order of column rules.
- Resolved: Columns do not clip anything. (As if
::column just had overflow:visible by default).
- Resolved: Remove the restriction about overflow columns only being in continuous media with the statement that
column-fill has no effect on overflow columns.
- Resolved: Have two keywords for balancing –
balance and either balance-last or balance-all, depending on what implementations (including Prince and Antenna House) do by default.
- Resolved: To balance columns, you just make the row as short as possible (honoring breaking controls, sizes, etc.), then flow normally into that height. No explicit “balancing” occurs (but it’s a common effect).
- Resolved: Håkon to create a public, editable, full list of issues with source, response and resolution. The format is up to him.
Full Minutes
Spec Discussed
Shapes and Regions
- Mihai Balan to become test owner for Regions.
- Resolved: Conditional agreement on taking Shapes to Last Call. The final yay/nay will be at the telcon in two weeks.
Full Minutes
Spec Discussed: Regions Shapes
Transforms
Discussed possible syntaxes additions for making transform lists easier to interpolate. One idea discussed was using commas to group transforms. This had a number of disadvantages, one of which is incompatibility with SVG syntax. Another idea was introducing a null transform, which would be compatible with all transforms and to use as a placeholder in a list. No conclusions and no changes to this level.
There was also a brief diversion into the idea of editing only one segment of a list-valued property.
Full Minutes
Spec Discussed
Minutes Telcon 2013-09-25
- Resolved: RESOLVED: Publish CSS Compositing and Blending Level 1 as Last Call.
- Everyone will review GPCM and Page Floats for next week’s telecon.
- Resolved: TabAtkins to put
overflow: clip to new Editor’s Draft.
- Resolved: Use
doubles instead of float for matrix items.
- Remaining issues for
DOMMatrix, DOMPoint and DOMPointLiteral were deferred until next week.
- The group discussed the need for and use of
device-cmyk(). No conclusion was reached by the end of time, so the discussion will be continued on the mailing list.
Full minutes
CSS Syntax Draft Updated
The CSS Working Group has published an updated Working Draft of CSS Syntax. This module describes, in general terms, the basic structure and syntax of CSS stylesheets.
This is a complete rewrite of the obsolete 2003 draft. It describes CSS tokenization and parsing in imperative recursive decent style, and exhaustively covers error handling. Additionally, the An+B syntax used in :nth-child() and related Selectors is not described in terms of the same tokenizer as the rest of CSS.
Changes since CSS 2.1 are listed in the Changes section.
As always, please send feedback to the (archived) public mailing list www-style@w3.org with the spec code ([css-syntax]) and your comment topic in the subject line. (Alternatively, you can email one of the editors and ask them to forward your comment.)
CSS Ruby Level 1 Published
The CSSWG published a Working Draft of CSS Ruby Level 1 this week. This module describes the rendering model and formatting controls related to displaying ruby annotations in CSS.
The new draft extends the model to handle HTML5 ruby markup, and adds details on box generation, layout, alignment and justification, white space handling, line breaking, and various other details. In addition, the CSS properties offering control over ruby layout have been reduced, simplified, and aligned better with existing CSS controls in other layout models. Significant changes since the 2003 version are listed in the Changes section.
Comments are welcome on all aspects of this draft. As it’s a rather radical rewrite of the old spec, this is essentially a “first” draft of the CSS Ruby model, and we would appreciate feedback on the correctness and reasonableness of all the newly-specified details.
As always, please send feedback to the (archived) public mailing list www-style@w3.org with the spec code ([css-ruby]) and your comment topic in the subject line. (Alternatively, you can email one of the editors and ask them to forward your comment.)
Updates to CSS Grid Layout
The CSS Working Group has published an updated Working Draft of CSS Grid Layout Level 1. This CSS module defines a two-dimensional grid-based layout system optimized for user interface design.
There were lots of changes since the last Working Draft, including:
Renaming
As resolved in May as part of the Logical Directions Renaming, we’ve updated the grid placement longhand properties to be grid-row-start/grid-row-end/grid-column-start/grid-column-end with the shorthands grid-row/grid-column and grid-area. (We expect authors to use the shorthands most frequently.)
As discussed at the Tokyo F2F in June, we also renamed the grid-definition-rows/columns properties to grid-template-rows/columns, and changed grid-template to grid-template-areas. This gives all the properties defining the explicit grid the same prefix. (We also added a grid-template shorthand, for good measure.)
Shorthands
We adopted the grid shorthand syntax from the Template Layout module and added the ability to set values for auto-formatted grids. The template shorthand syntax allows authors to visually associate the various row and column measurements with their respective rows and columns in the named template areas.
Named Lines
The previous named lines syntax was pretty awkward, as pointed out in this thread. It also used strings as CSS-internal identifiers, which we don’t do anywhere else. We adopted the proposal from that thread, which was to switch to identifiers and use parentheses to group multiple names for the same position. This has the benefit of
- Using identifiers, consistent with the rest of CSS
- Providing visual grouping of names that identify the same location
- Allowing the named grid areas template syntax (which uses strings) to co-exist with named lines in the grid-template shorthand.
A more subtle change to named lines is that named grid areas now implicitly create named lines corresponding to their start and end edges, so you can more easily position something to the start or end edge of a particular named grid area without having to explicitly name those lines.
Other Changes
We’ve also clarified how absolutely-positioned items interact with the grid-placement properties, defined the static position of grid container children, rewrote and fixed errors in auto-placement algorithm.
And last but not least, we redesigned the subgrids feature, which allows alignment across the contents of a grid container’s immediate children.
Moving Forward
We still have some open issues, in particular some open discussion around the grid-auto-flow, that we hope to resolve soon. After that we expect most of the high-level design work to be complete, and then we’ll be digging into the gnarly layout details until we iron them all out. 
Feedback
As always, please send feedback to the (archived) public mailing list www-style@w3.org with the spec code ([css-grid]) and your comment topic in the subject line. (Alternatively, you can email one of the editors and ask them to forward your comment.)
Minutes Telecon 2013-09-04
- Resolved: Change
UNICODE-RANGE token (in Syntax & CSS2.1) to be more restrictive in what it accepts, per Tab’s proposal. (No changes to Fonts.)
- Resolved: Transition CSS Fonts Level 3 to Candidate Recommendation.
- Resolved: Transition CSS Cascade Level 3 to Candidate Recommendation.
- Resolved:
text-combine-horizontal doesn’t disable font-variant: full-width. Revisit if fonts start to become popular that would benefit from this extra interaction.
- Discussed improving gradient stop color fixup rules for better transitions.
- Discussed handling Media Queries 3 errata.
Full minutes
Archives
Browse by date:
Browse by category:
![[Photo: group photo of the CSS working group in Lyon, France]](/web/20131010105921im_/http://www.w3.org/Style/CSS/csswg-2010.jpg)
Contact: