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, and the Future of CSS syndicator.
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.
W3C and La Cantine invite the Web community of Paris (France) to the third W3C Meetup at La Cantine. The theme this time is CSS. The event will be held the evening of February 8, with participation of several members of the CSS working group. There will be presentations & demos in both English and French. Discussions can be in both languages; Daniel Glazman will translate between the two.
The program includes presentations by Daniel Glazman (Disruptive Innovations, co-chair of the CSS WG), Vincent Hardy (Adobe) and David Baron (Mozilla). Entrance is free, but registration is required.
The address of La Cantine is 151 rue Montmartre, 75002 Paris, between the metro stops Grands Boulevards (lines 8 & 9) and Bourse (line 3). The time on Wednesday February 8 is from 19:00 to 21:00.
currentColor
keyword, which computes on the element specified and then inherits, instead of inheriting as a keyword and then recomputing on each element. This is okay for non-inheriting properties like border-color
, but doesn’t work for properties that inherit, like text-emphasis-color
. (It effectively defaults the property to the color
of the root element.) Tab to investigate whether SVG depends on this behavior or if we can change it.
The CSS WG has published a Last Call Working Draft of the CSS3 Image Values and Replaced Content. This module covers:
element()
notation for using an elements’ graphical representation as an image.
object-fit
and object-position
for controlling aspect ratio preservation.
image-resolution
for using explicit or intrinsic image resolutions.
image-orientation
to correct mis-rotated images.
Note that replaced elements in CSS includes not just bitmap images, but also SVG (external or embedded), video, applets, plugins, and other “foreign” objects.
There have been significant changes to gradients over the past year.
If you have comments on any part of the draft, please, send them to the (archived) www-style@w3.org mailing list. Start a new thread for each issue, and include [css3-images]
in the subject line. This will help us track your comments. (And please, if you can’t/won’t post to www-style, email the editors instead of posting randomly into the ether.)
We welcome editorial suggestions, additional examples, diagrams, or anything else that will help to make the spec more understandable.
The official deadline for comments is 7 February 2012. Let us know if you need an extension so that we don’t miss your comments.
text-overflow:ellipsis
outlined in Tantek’s email
!important
in animations rules – it’s a syntax error.
!important
rules to override animations (exact location of animations in the cascade level still undetermined)
Tab Atkins and I published an updated Working Draft of CSS Image Values and Replaced Content Level 3 this month. We anticipate that this will be the last draft before Last Call, which we aim to publish in January. If you have an interest in this draft, please review it and send in your comments.
Below is a summary of the major changes to CSS gradients over the past year:
linear-gradient()
changed from polar angles to bearing angles (compass directions). 0° now points up (bottom-to-top), and angles increase clockwise. See Angles in Gradients for the feedback that informed this decision.
linear-gradient()
changed from bare directional keywords (top
, right
, bottom
, left
) indicating the starting point to to <keywords>
where the keyword indicates the endpoint. (to bottom
, to left
, to bottom
, to left
). This change was made because Tab felt having 0deg
mean bottom-to-top made the fact that top
meant top-to-bottom confusing. The WG was split but mostly ambivalent on whether this was necessary, or whether from <keyword>
was a better alternative; the resolution landed on to <keyword>
.
linear-gradient()
has been redefined so that instead of aligning the gradient line to the diagonal, the central color occupies the other diagonal. See Behnam Esfabad’s post for a demonstration showing the old and new (“magic”) versions.
radial-gradient()
has been changed to (roughly) radial-gradient( [ <shape> || <size> ] [ at <position> ]?, <color-stop> [ , <color-stop> ]+)
: specifically, the shape/size and position parameters are collapsed into the first argument using CSS property value conventions, allowing either or both to be specified. Position is distinguished from size by the preceding at
keyword. See Radial Gradient Readability for some of the thinking that went into this change.
Although CSS gradients are undoubtedly the most anticipated feature in CSS3 Images, there are a number of other features in this draft:
image()
notation, which can be used in place of url()
, allows authors to trigger CSS parser fallback in older UAs when using media fragments.
image()
notation allows specifying a list of fallback images in various formats and allows annotating images with left-to-right or right-to-left directionality so that they flip automatically to match the element’s directionality.
object-fit
property allows preserving the aspect ratio of an image when assigning its box a specified size. In conjunction with the min/max-width/height
properties, it also allows scaling the image and its box up to a given maximum, or down to a given minimum. The object-position
property allows repositioning the image within its content box using background-positioning sytax when object-fit
causes the aspect ratio of the image and the content box to mismatch.
image-resolution
property allows for using bitmap resolutions other than 1 image pixel == 1 CSS px unit.
As always, send feedback to www-style with the spec code ([css3-images]
) and your comment topic in the subject line. While posting to www-style is preferred, I’ve also cross-posted to CSS3.info, and we’ll be scanning the comments there for issues, too.
appearance
property dropped from CSS3 UI
pointer-events
or how to keep it without destabilizing CSS3 UI
Last week the CSSWG published updates to four layout-related CSS specs:
[css3-flexbox]
)[css3-layout]
)chains
property to combine multiple slots in a template into a single one, in order to create areas with complex and disjoint shapes; and a larger number of properties that apply to slots: the style of a slot in turn influences the style of the elements placed inside it (region-based styling).[css3-regions]
)[css3-gcpm]
)Template Layout relates closely to Grid Layout, Flexbox, and Regions; however, these high-level layout modules have yet to be fully integrated.
As always, send feedback to www-style with the spec code ([css3-flexbox]
, [css3-regions]
, [css3-layout]
, or [css3-gcpm]
) and your comment topic in the subject line.
radial-gradient( [ <shape> || <size> ]? [at <position> ]?, ... )
Browse by date:
Browse by category: