CSS WG Blog » publicationsCascading Style Sheets Working Group Blog2015-03-26T10:25:25Zhttp://www.w3.org/blog/CSS/feed/atom/WordPressfantasaihttp://www.w3.org/blog/CSS/?p=25062015-02-28T18:23:12Z2015-02-28T18:22:22Z]]>The CSS WG has published an updated Working Draft of the CSS Fragmentation Module Level 3. This module describes the fragmentation model that partitions a flow into pages, columns, or regions and provides controls for breaking.

We expect this to be the last WD before CR, and plan to transition at the end of March. Please review and send us any comments. If you plan to review but aren’t sure you have time, send us a note so that we know to wait for your comments.

As always, please send feedback to the (archived) public mailing list www-style@w3.org with the spec code ([css-break]) and your comment topic in the subject line. (Alternatively, you can email one of the editors and ask them to forward your comment.)

]]>0fantasaihttp://www.w3.org/blog/CSS/?p=24892015-01-15T21:52:47Z2015-01-15T21:52:47Z]]>The CSS Working Group has published an updated Working Draft of CSS Pseudo-elements Level 4. This module describes the syntax, styling, and inheritance/cascading models for each of the existing CSS pseudo elements, re-introduces ::selection (with a much more comprehensive description of how it’s supposed to work), and introduces a few new ones, such as ::placeholder.

As always, please send feedback to the (archived) public mailing list www-style@w3.org with the spec code ([css-foo]) and your comment topic in the subject line. (Alternatively, you can email one of the editors and ask them to forward your comment.)

]]>0fantasaihttp://www.w3.org/blog/CSS/?p=24682014-12-19T21:48:54Z2014-12-19T07:49:11Z]]>The CSSWG has published an updated Working Draft of CSS Box Alignment Level 3. This module defines extends the Flexbox alignment properties to apply to all layout models and adds additional controls for logical positioning, space distribution, and handling overflowing elements.

This is the vertical centering module, people.

This module’s syntax and functionality is in the process of stabilizing now and we need your feedback. Think of all the cool things you could do with the new alignment properties! Imagine them! Examine them! Make examples! Write rants! And tell us what is awesome and what is stupid so that we can fix it to be better before it gets locked down in shipped browsers.

As always, ideally send feedback to the (archived) public mailing list www-style@w3.org with the spec code ([css-align]) and your comment topic in the subject line. Alternatively, post your comment here or in the more discussion-friendly CSS3.info cross-post. (Or, if that’s still too scary, email the editors directly.) Please do not expect us to go fishing for your comments in the ether. We won’t know it’s there and we will therefore deliberately and mercilessly ignore it. If it’s on your blog, email the link or post it as a comment. It’s super not that hard. Thanks.

]]>0Alan Stearnshttp://www.w3.org/blog/CSS/?p=24002014-10-09T21:13:42Z2014-10-09T21:13:42Z]]>The CSS Working Group has published an updated Working Draft of CSS Regions Level 1. CSS Regions gives the ability to say, “Display this content (a named flow) over there (a region chain).”

The changes from the last public working draft are only in the introduction. You may have looked into CSS Regions in the past and thought to yourself, “Magazine-style layout isn’t relevant to me.” If you have, please take a look at the new intro which now shows much more basic examples and motivations for the feature.

Please send feedback to the (archived) public mailing list www-style@w3.org with the spec code ([css-regions]) and your comment topic in the subject line.

(Alternatively, you can email one of the editors and ask them to forward your comment.)

]]>0fantasaihttp://www.w3.org/blog/CSS/?p=23842014-09-27T20:00:03Z2014-09-27T19:54:18Z]]>About a fortnight ago, the CSS WG published an updated Working Draft of the CSS Display Level 3. This module describes how the CSS formatting box tree is generated from the document element tree and defines properties (like the display property) that control the types of boxes thus generated.

Significant changes since CSS2.1 include:

Splitting display into display-inside and display-outside to independently control the layout mode inside the box and its role in the parent formatting context, respectively.

Adding an independent “noneness” switch that does not overwrite the box type declaration. (This will make it way more straightforward to dynamically show/hide content.)

Reintroducing display: run-in, but with more reasonable behavior than was in CSS2.1 before it was dropped.

Adding a display: contents value that eliminates the element’s own box and brings its children up to act as children of its parent box.

Figuring out an ideal interaction for the new show/hide switch and its equivalent (the speak property) from CSS Speech. (Likely we’ll make speak: auto depend on the value of box-suppress, but we’re open to other considerations.)

Our plan going forward is to resolve all the open issues (obviously), defer the longhands of display to another level[1], and hopefully transition to CR in the next six months.

As always, please send feedback to the (archived) public mailing list www-style@w3.org with the spec code ([css-display]) and your comment topic in the subject line. Alternatively, you can email the editors and ask them to forward your comment, or post a comment here.

]]>0fantasaihttp://www.w3.org/blog/CSS/?p=23802014-09-27T18:17:26Z2014-09-27T18:17:26Z]]>The CSS Working Group has published another Last Call of CSS Flexible Box Layout Level 1 in response to feedback on the recent changes. Flexbox is a new layout model for CSS: the contents of a flex container can be laid out in any direction, can be reordered, can be aligned and justified within their container, and can “flex” their sizes and positions to respond to the available space. This is an update to fix various problems, particularly in the layout algorithm, found through implementation review and experience during the Candidate Recommendation phase. As before, the CSSWG is not revoking the call for implementations: we’re just issuing an LCWD to process the changes.

To help with review and with correctly updating implementations, exact diffs since the original Candidate Recommendation, and their justifications, are available in the Changes section. A Disposition of Comments is also available. The Last Call comment period ends 25 October 2014: please either send comments by then, or request an extension; we plan to process them during TPAC.

As always, please send feedback to the (archived) public mailing list www-style@w3.org with the spec code ([css-flexbox]) and your comment topic in the subject line. (Alternatively, you can email one of the editors and ask them to forward your comment.)

]]>0Alan Stearnshttp://www.w3.org/blog/CSS/?p=23692014-09-16T21:02:32Z2014-09-16T21:02:02Z]]>The CSS Working Group has published an updated Working Draft of CSS Line Grid Level 1. CSS Line Grid defines features for aligning content to a baseline grid.

The changes from the first public working draft are mainly cleaning up and removing features for the first level of this specification:

Added line-snapping examples

Modified box-snap values

Removed line-slack

Removed grid offset

Removed grid units

Removed 2d box snapping

Removed rounding functions

Please send feedback to the (archived) public mailing list www-style@w3.org with the spec code ([css-line-grid]) and your comment topic in the subject line.

(Alternatively, you can email one of the editors and ask them to forward your comment.)

]]>0Dirk Schulzehttp://www.w3.org/blog/CSS/?p=23112014-05-23T15:28:29Z2014-05-23T15:28:29Z]]>The CSS Working Group and the SVG Working Group have published an updated Last Call Working Draft of CSS Masking Level 1. CSS Masking provides two means for partially or fully hiding portions of visual elements: masking and clipping.

Renamed mask-box* properties and terms to mask-border*.

Added support for multiple mask layers. (Similar to multiple background layers for background.)

Added the mask-composite property to control compositing of multiple mask layer images with the keywords add, subtract, intersect and exclude.

Please send feedback to the (archived) public mailing listpublic-fx@w3.org
with the spec code ([css-masking])
and your comment topic in the subject line.
(Alternatively, you can email one of the editors and ask them to forward your comment.)

]]>0Dirk Schulzehttp://www.w3.org/blog/CSS/?p=23092014-05-23T17:24:05Z2014-05-23T15:18:36Z]]>The CSS Working Group and the SVG Working Group have published a First Public Working Draft of Geometry Interfaces. This specification provides basic geometric interfaces such as DOMPoint, DOMRect, DOMQuad or DOMMatrix used by other modules or specifications.

Implementation is already proceeding in Firefox and prefixed implementations are shipping in Safari, Chrome, Opera and Internet Explorer.

Please send feedback to the (archived) public mailing list public-fx@w3.org with the spec code ([geometry]) and your comment topic in the subject line. (Alternatively, you can email one of the editors and ask them to forward your comment.)

]]>0fantasaihttp://www.w3.org/blog/CSS/?p=22782014-04-11T22:21:04Z2014-04-11T22:21:04Z]]>The CSS WG has published First Public Working Drafts of two new modules:

Defines various scoping/encapsulation mechanisms for CSS, including scoped styles and the @scope rule, Shadow DOM
selectors, and page/region-based styling.

These are early-stage working drafts: the features described therein are not well-baked and may change dramatically or be removed. We’re soliciting comments on both design and details of these features, and implementers should participate in the design-level discussions happening on www-style before considering implementation.

As always, please send feedback to the (archived) public mailing list www-style@w3.org with the spec code ([css-line-grid] or [css-scoping]) and your comment topic in the subject line. (Alternatively, you can email one of the editors and ask them to forward your comment.)