Bert Bos,
CSS contact
(This page uses CSS style sheets)
W3C and the CSS Working Group publish information about the specifications under development in various ways. This page is the working group's weblog (blog). Other places to find information are the “current work” page and the www-style mailing list.
The CSS WG looked, among other things, at the stability of the Backgrounds and Borders module and an issue with replaced elements and 'run-in' in CSS 2.1.
There was also news about Selectors: after seeing the number of implementations, the Director agreed to give the specification Proposed Recommendation status. The review period will start in a few days.
the shadow is cast by a negative of the alpha channel, then clipped to the actual alpha channel)
The pieces we'd need to address, in various combinations: background layers, border (one piece), content (one piece)) Only adjacent layers would need to be composited together. Drop shadows would then paint immediately below the composited layer. See also fantasai's message on this topic.
filter property would be able to
address these use cases, particularly if parametrized canned filters were
added for commonly desired effects and CSS targets were added e.g. as
described by roc.It is proposed to add media queries to <video> and then
to also define queries for the user's special needs. These new media queries
will go into a new media queries module.
Reviewed status of CSS2.1 test suite. Still on track wrt roadmap. fantasai has a rough coverage report, but is missing many of Microsoft's tests because they don't have the right metadata. (Microsoft's management is preventing Arron from correcting the tests.)
color-correction property with
values default and srgb where default
is UA-defined and srgb corrects untagged images to sRGB.display: run-inWorked through issues summarized in Bert's email
::first-lines and run-ins.Reviewed examples of copyfitting by changing the font size and various past proposals for addressing some of the use cases. Intentions can be split into:
dbaron proposes a copyfit property to trigger these behaviors. An alternate
proposal is to incorporate this into text-justify.
Related behaviors were mentioned: specifically, triggering justification on the last line only if it's longer than a certain threshold; and specifying a minimum length for the last line, which would trigger whole-paragraph justification if the last line were not long enough.
Conclusion is to add some notes to css3-text and leave it for the next active editor to deal with.
font-variant and font feature support in CSSJohn Daggett proposes adding subproperties to font-variant
for allowing access to the more common OpenType features. font-variant
would become a shorthand for font-variant-ligatures,
font-variant-alternates, font-variant-caps,
font-variant-numeric, font-variant-position.
There some concern about fallback behavior for subscript and superscript features, and winding up with either a complete loss of semantics or a double-sub/superscript rendering.
John notes that OpenType has language-sensitive rendering, and proposes allowing an explicit choice of typographic language different from the content language.
There's concern about exposing alternate glyphs from a generic mechanism such as font-variant, because the choices are very font-specific. Proposals include dealing with it in @font-face; and pairing the glyph set number with the font name so that it only triggers on that font name.
Otherwise the WG is mostly in agreement and pressures jdaggett into putting his proposal in the editor's draft. :)
text-overflow: ellipsisResolved: Only horizontal overflow triggers for text-overflow: ellipsis. Add a new keyword for handling ellipsis due to vertical overflow (where the ellipsis appears on the last line only).
Discussed other issues with text-overflow, including:
overflow, whether it prevents overflow, whether
it requires overflow: hidden, what happens with overflow: scroll,
how that makes sense with floats, etc.Apparently some of these questions were resolved over lunch.
Full minutesex definition to be changed to use the parent's element font size if set on font-size (just like em) Rationale: Avoid infinite loops in the spec. :)0.5em fallback in CSS3 Values for when ex height cannot be found.The CSS Working Group just published a Last Call for Comments Working Draft of CSS Backgrounds and Borders Level 3. Please review the draft and send your feedback. We'll be accepting comments through 17 November 2009. (Note that feature requests are likely to be deferred to CSS4.) The best place for feedback is the CSSWG's official mailing list www-style@w3.org, but we'll also look at any comments posted (or linked to) from the cross-post on CSS3.info.
There are a couple issues we're specifically looking for feedback on:
The round option for background-repeat
and border-image-repeat resizes images to fit the nearest
whole number of tiles, rather than always scaling up or always scaling
down. Rounding keeps closer to the intended size and, in the case
where one dimension is fixed (e.g. in ‘border-image’), keeps the image
closer to the intended aspect ratio. This is almost certainly the best
solution for vector images and high-resolution raster images. However,
if the given image is a low-resolution raster image, it will require
interpolating pixels, which can look bad. See "Rounding Extremes" for
illustrations.
The workaround is to specify a higher-resolution image (e.g. by shrinking from the original with background-size or border-image-width). Possible spec solutions include introducing a separate keyword that always scales down, and changing the algorithm so that we force scaling down whenever interpolation would be required for scaling up. So the options here are
round, but I want an extra keyword to force downscaling in all cases (including vector images) because [...].Please comment on what you prefer and why. (The more specific you can be "for example, this image that I would want to use [...]", the easier it will be for us to understand your point.)
The previous
draft included two properties for controlling behavior at box
breaks (line breaks / column breaks / page breaks):
border-break for controlling whether the border is drawn
at the break, and background-break for controlling
whether the background is drawn for each box individually or for the
whole element as if it were broken after painting.
Hyatt suggested merging the two, so the current draft has a single
box-break property instead. The two values mean,
basically, "render backgrounds and borders for this box, and then
slice it up" and "break the box and then render backgrounds and
borders for each box individually". The value names aren't
particularly clear, however, so we were wondering if anyone has better
ideas.
So take a look at the new draft and send us your comments! This is your last chance to give feedback on this module: if all goes well, we'll be publishing the Candidate Recommendation in time for Christmas, and given the state of experimental implementations right now, I expect things to move rapidly from there.
column-rule-color to CSS3 Color vs CSS2.1.text-justify property; the issue is deferred to the next active editor.round keyword for background-repeat and border-image-repeat scales to the nearest whole number of tiles. This will be marked as an issue for feedback in case people prefer different behavior or would like additional controls (e.g. round-up or round-down) keywords).border-radius. They refer to a percentage of the corresponding dimension of the box (so border-radius: 50% gives an oval).box-shadow from CSS Backgrounds and Borders Level 3: work on box-shadow outside the module for the time being, possibly re-merge with draft later. Rationale: drop-shadows seem to need a lot more discussion, but the rest of the draft is ready to move on.border-image resizes to fit small boxes the same way as border-radius (proportional in both dimensions)