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.
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.
position: grid to pull descendant elements up into an ancestor grid.
auto offsets meaning use padding edge of containing block.
grid-definition-* and 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.
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.
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.
Discussed Last Call publication of Counter Styles and linking to Internationalization WG’s Counter Styles NOTE.
!important interplays with scoped styles; current spec is good.
default, remove issue, but also clarify the spec and add examples.
inherit-or-initial depending on whether property inherits by default.
Discussed SVG use case of including more details as user zooms in, e.g. on a map. While discussing how to solve this, it became clear that while people have some idea of how zooming is interpreted wrt Media Queries, the whole interaction of resolution and resizing is vastly underdefined and needs work before we can sensibly add related new features.
Discussed possibilities of cross-site attacks via CSS. One case that krit brought up wrt importing shapes was dismissed as Not a Problem. Some others raised by roc & bz might need more thought and discussion.
pointer-events: elements-from-point solution that will walk the elementsFromPoint() chain instead of the ancestor chain (problem is passing events from content to fragmentation container)
::pseudo:pseudo combinations are invalid or match nothing.
Brian Birtles presented the Web Animations editor’s draft with an overview of its contents. (See also diagram.)
Dean Jackson of Apple expressed some concern at adding so much API to
the Web platform at once:
[We’re] concerned about the massive amount of new API to add in one step. Generally Web improvements are more successful when iterative rather than massive new feature.
And also expressed that
Apple’s main interest in this type of work is very much in the form of declarative approaches to animation backed by a strong API.
and so there was some concern over leaving out features needed for declarative control.
However, everyone agreed that the spec was in good shape for FPWD, so
P.S. There is an experimental JS shim for the draft available.
The CSS and SVG WGs discussed the possibility of reusing the SVG stroke and fill properties to stroke and fill text in CSS. Some concerns raised:
color
fantasai and Tab volunteered to draw up a proposal for how this should work
Discussed SVGWG’s proposals ([1], [2]) for adding soft-wrapping to SVG. The goal is to re-use CSS functionality (and layout engines) for SVG text layout. No objections so far to proposal to add a width attribute to <text> for wrapping; however it was felt by some that for formatting multi-block content, HTML markup should be reused. In general, people want CSS text formatting to Just Work in SVG, not require special rules for SVG text content.
Reviewed Compositing and Blending draft, which now contains only 3 CSS properties: mix-blend-mode, isolation, background-blend-mode. Discussed use cases, design, interaction with stacking contexts, forwards-compatibility, etc. The draft needs more review. Meanwhile,
The CSS Working Group and the SVG Working Group have published an updated Working Draft of CSS Masking. CSS Masking provides two means for partially or fully hiding portions of visual elements: masking and clipping.
With this draft, CSS Masking integrates better with terms and definitions of the CSS Backgrounds and Borders module. The syntax of the ‘mask’ shorthand property is conformant with the ‘background’ shorthand property. Authors can switch between alpha and luminance masking on mask-image now. The IDL definitions of SVGMaskElement and SVGClipPathElement were adapted to use WebIDL.
Changes since the last Working Draft are listed in the Changes section.
Please send feedback to the (archived) public mailing list public-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.)
The CSS Working Group has published the First Public Working Draft of CSS Shapes.
This draft was previously part of the CSS Exclusions and Shapes specification. Exclusions and Shapes have been split out into two separate specifications, and this draft contains only the Shapes part. Future levels of these specifications will describe how these two features interact.
CSS Shapes extends wrapping behavior to shapes other than rectangles. The first level of CSS Shapes allows a shape to be applied to floats, so inline wrapping around a float can happen around an arbitrary shape. This draft includes a syntax for defining basic shapes, extracting a shape from the alpha channel of an image, and applying these shapes to floats using new shape-outside, shape-margin and shape-image-threshold properties.
All of the changes since this new draft was split from CSS Exclusions and Shapes are listed in the Changes section.
As always, please send feedback to www-style@w3.org with the spec code ([css-shapes]) and your comment topic in the subject line. (Alternatively, you can email one of the editors and ask them to forward your comment.)
background-attachment:local.
an+b grammar changes in Syntax 3.
font-size-adjust, font size availability.
background-attachment: local positioning.
The CSS Working Group has published an updated Working Draft of CSS Exclusions.
This draft was previously part of the CSS Exclusions and Shapes specification. Exclusions and Shapes have been split out into two separate specifications, and this draft contains only the Exclusions part. A new draft of CSS Shapes will follow shortly. Future levels of these specifications will describe how these two features interact.
CSS Exclusions allows content wrapping around any element, extending this functionality that has been limited to floats.
The first level of CSS Exclusions allows wrapping around the bounding box of an exclusion. This draft includes improvements to the exclusions processing model, a new value for wrap-flow, and clarification on how exclusions interact with writing modes.
All of the changes since the last Working Draft are listed in the Changes section.
As always, please send feedback to www-style@w3.org with the spec code ([css-exclusions]) 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 Working Group has published an updated Working Draft of CSS Regions.
CSS Regions allows you to collect content in a named flow, then directly define where this content flows through boxes in a region chain.
This new draft contains many improvements to the CSSOM section, as well as scattered improvements throughout. The issues list for CSS Regions has gone from 24 in the last draft to 4 today. The region-overset property has its new name, and the flow-into property now has keywords that choose whether an element or its content is placed into a named flow. Region styling is now accessed through a ::region() pseudo-element instead of an @region rule.
All of the changes since the last Working Draft are listed in the Changes section.
As always, please send feedback to 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.)
Browse by date:
Browse by category: