CSS WG Blog

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.

Minutes San Diego F2F August 2012: @supports, Selectors 4, Syntax

By fantasai August 30, 2012 (Permalink)
Categories: resolutions

CSS Conditional Rules Level 3

Discussed OM for @supports:

Resolved: Have intermediary condition rule interface called CSSConditionRule
Resolved: .conditionText on the common interface; for @media it is equivalent to .media.mediaText
Resolved: .conditionText returns either the token stream or source text from the style rule, with no logical simplifications, just tokenization ones
Resolved: CSS.supports() with one (conditionText-compatible) or two (property, value) arguments. Fall back to window.supportsCSS() if not possible.
Resolved: property name must be the name, no escapes, no spaces, it’s not parsed it’s just a name. value can be anything taken as a value

Selectors Level 4

Section added to define selector scoping. Better terminology suggestions welcome.
Discussed drag-and-drop selectors, see resulting summary.
Resolved: Add :user-error pseudo to represent :-moz-ui-invalid. Issue raised about potential :user-interacted.
Resolved: Publish next draft with subject indicator as a ! before the subject; issue open on whether before or after.
Resolved: Publish Selectors Level 4 as WD

CSS Syntax Level 3

Tab presented his draft of CSS Syntax Level 3, which is defines CSS parsing as a state machine, and asked for feedback. Some work still necessary before it’s ready to publish officially as WD.

Full minutes: @supports and Selectors 4, Syntax

CSS3 Text Draft Updated

By fantasai August 14, 2012 (Permalink)
Categories: publications

The CSS Working Group has published an updated Working Draft of CSS Text Module Level 3. The text module contains features relating to line-breaking, justification, white-space controls, and text decoration.

We are hoping this will be the last WD before Last Call, and would appreciate
everyone’s detailed review. Known open issues are listed on Tracker. Changes since the last Working Draft 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 ([css3-text]) 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 2012-08-08

By fantasai August 14, 2012 (Permalink)
Categories: resolutions

Resolved: Publish updated WD of CSS3 Text
Resolved: Accept dbaron’s overflow: repeat/regions draft as ED work item
Status update on CSS3 Conditional Rules: @supports implemented by Opera and Gecko teams; Opera has submitted tests. Some open issues on OM section drafted last month—will be discussed next week prior to updating WD.
Briefly reviewed run-ins discussion
Resolved: auto margins in grid layout behave like they do in flexbox
Phil summarized the two main proposals for handling unpositioned grid content:
- Automatically grid items, same way as Flexbox
- Flow all unpositioned content into an anonymous grid item, pulling out any grid-positioned elements directly into the grid
Resolved: Errata CSS2.1 to say that overflow on a table element applies to the table box (not table wrapper box); and that values other than hidden are treated as visible.

Full minutes

Minutes Telecon 2012-08-01

By fantasai August 2, 2012 (Permalink)
Categories: resolutions

Resolved: Publish FPWD of the Compositing draft.
Resolved: The order property affects absolutely-positioned flex items.
Resolved: Flexbox goes to Candidate Recommendation.
Discussed interpolation of transforms
Resolved: Accepted the following clarifying edits to CSS2.1: Edit 1, Edit 2, Edit 3, Edit 4.
Discussed whether/how overflow applies to table elements.

Full minutes

Minutes Telecon 2012-07-25

By fantasai August 2, 2012 (Permalink)
Categories: resolutions

Resolved: Placeholders have no impact on surrounding flex layout.
Resolved: Static position of absolutely-positioned flex items defined according to principles used in normal flow. Editors to work out exact text.
Resolved: The order property does not apply to absolutely-positioned children of a flexbox; placeholders have all initial/inherited values for properties. [Reverted]
Resolved: Fix issue 22.

Full minutes

Minutes and Resolutions Telecon 2012-07-18

By fantasai August 2, 2012 (Permalink)
Categories: resolutions

Resolved: Accept ChrisL’s suggested change to the note about deprecating system colors in CSS3 Color.
Resolved: Accept Florian’s proposal for defining the return value of removeProperty.
Resolved: Drop resolution descriptor from CSS Device Adaptation.
Default font features must be on by default, for now; MSFT to conduct some perf testing, jdaggett to investigate adding none values to turn things off.
Resolved: For Issue 10, alignment of over-constrained block-level flex containers remains dependent on containing block’s direction; flex-flow is not consulted. (No change.)
Resolved: For Issue 14, visibility: collapse redoes line breaking, as there are good reasons to want that. (No change.)
Resolved: For Issue 4 the order property is not renamed to better indicate that it only affects visual rendering (and not speech or tab-order) because it’s too late in the process and the WG doesn’t know of a significantly better alternative.
Handling of abspos placeholders in flex containers (issues 17 and 18) is up as a topic for next week.

Full minutes

Minutes and Resolutions Telecon 2012-07-11

By fantasai July 11, 2012 (Permalink)
Categories: resolutions

Resolved: Negative durations are invalid for transitions/animations.
Resolved: Move feature requests for new animation APIs to Level 4.
Resolved: Defer the <ident> generic type until Level 4 of Values and Units.
Resolved: The request to change calc() to just () is rejected; calc is required at the outer level.
Resolved: Spaces are required around addition/subtraction operators; no change from previous resolution.
Resolved: Disposition of Comments for CSS3 Values and Units is accepted; move spec to Candidate Recommendation.
Resolved: Flex items do not create a pseudo-stacking context at this point, since there is no strong reason to make a change.
Resolved: Non-auto values of z-index create a stacking context on flex items even without position: relative.

Full minutes

Minutes and Resolutions Telecon 2012-07-04

By fantasai July 4, 2012 (Permalink)
Categories: resolutions

Resolved: Use about:invalid as the fallback url in attr().
Resolved: Defer Appendix A of Values and Units to L4
Resolved: Defer issue 28 (normalization of <custom-ident>) to L4
Resolved: No change to calc() white space rules; they are required around + and -, and optional around / and *.
Resolved: Flexbox order property does not affect tab order or speech order
Resolved: Rename order to something more specific so it doesn’t imply that non-visual orders (e.g. tab order or speech order) are affected.

Full minutes

Minutes and Resolutions Telecon 2012-06-27

By fantasai June 27, 2012 (Permalink)
Categories: resolutions

Resolved: All elements, regardless of display value, are promoted to being flex items when placed in a flex container.
Resolved: Added vmax unit.
Resolved: calc() inside calc() allowed.
Resolved: Publish updated CR of CSS3 Backgrounds.
Discussed edits to CSS2.1 wrt “formatting context” terminology, and whether overflow applies to table elements.

Full minutes

Minutes and Resolutions Telecon 2012-06-20

By fantasai June 20, 2012 (Permalink)
Categories: resolutions

Resolved: Proposed edits to CSS2.1 accepted pending dbaron’s review and acceptance.
Resolved: order affects painting order.
Discussed handling of replaced elements as flex items; fantasai to summarize discussion for resolution next week
Discussed how to handle background-attachment: fixed; in transformed elements; vendors to investigate their implementations.
Resolved: Add recto/verso values to (page-)break-before/after in CSS3 Fragmentation.