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.
This message from Daniel Glazman, with his CSS WG Co-chair hat on:
Yes, we need you. CSS 2.1 is a complex specification, and it has roughly 20,000 HTML4 and XHTML1 tests in its Test Suite. To make the document move from Candidate Recommendation to Proposed Recommendation, we need to show that each and every test in that Test Suite is passed by at least two different implementations. And that's where you can help:
If you have a few spare cycles and are able to test a few hundreds or thousands of the tests in the Test Suite with the latest version (see below) of Opera, Firefox4beta, IE or WebKit, please help us.
The results are aggregated into a database. Thanks a lot for your help!
Builds to be tested (and only those ones please):
John Daggett from Mozilla took Microsoft's marketing dept. to task for publishing PR articles using test results from unreviewed Microsoft tests "that wouldn't even pass Microsoft's internal review" while implying that they were accepted by W3C.
Advice for the future use of test results in marketing materials include:
jdaggett reviewed the font-variant-* features. Comments included:
font-variant-ligatures should note that it doesn't affect required ligatures.font-variant-alternates in a way that does not tie the numbers to specific fonts, the problem being that the numbered options would be applied to fallback fonts, resulting in unexpected glyph selections. jdaggett protested that this isn't a problem in reality while Adobe asserted that it will become more and more of a problem over time as use of advanced font technology increases. Several alternatives were proposed:font-feature-settings syntax by using idents and functional notation in place of strings. Bert noted that this may conflict with things like attr(), so the WG suggested prefixing each value with ot-. Also discussed error-handling.font-language-override's values are OT lang codes, not ISO lang codes. One suggestion was to accept ISO lang codes as idents and OT lang codes as strings.:ttb solution, since it is supposedly a pseudo-class, but is selecting a property of the UA, not of the element. Media Queries are seen as a more appropriate place to detect features of the UA environment.Resolved: Add #rrggbbaa to CSS4 Color.
ointer-events and overflow-x/overflow-y).::selection: WG agrees with all of them; problem is now a matter of defining a model that accommodates all of them.Discussed request for list-style: auto: Authors can already map list styles to languages with :lang(), so this feature does not seem necessary. Also, it would require a great deal of research to specify adequately. The CSSWG would consider adding the feature described if someone else did the necessary research to draw up an exhaustive table mapping lang codes to list-style-types and the Internationalization Working Group approved it.
A new group at W3C is planning to draw up requirements for Indic layout, similar to the JLTF efforts.
Discussed Hyatt's proposal
to alter syntax to make prefixing easier (which has the side effect of making the style sheet easier to understand, especially for someone unfamiliar with the Template module). The WG votes to add slot() notation to the 'position' values and to wrap the template strings in functional notation rather than add a new property as in Hyatt's proposal.Proposed to move CSS3 Values and Units to Candidate Recommendation to get calc() out. Starting by trimming any unfinished features and drawing up an at-risk list in prepartion for Last Call. This would mean: dropping fr and gr units, since they aren't standalone units anyway; and marking vh, vw, vm, and min() and max() at-risk.
Håkon would like to prepare the module for CR. Several people feel many of the features would be better placed in more appropriate modules, e.g. hyphenation to CSS3 Text. Some features may be underdefined. But nobody objected to any of the features fundamentally.
Wrt hyphenation:
hyphenate-resource property with an at-rule that maps language tags to hyphenation resources, since hyphenation resources need to be specified per language, but not per element. E.g.
@hyphenate-resource {
en-US: url(en-US.hy);
en: url(en-GB.hy);
fr: url(fr.hy);
}
This could also allow more intelligent lang-code→dictionary mapping than using :lang() selectors and a property.Reviewed several other features including:
line-box-contain, which needs more investigationResolved: Publish CSS Styling Attributes as Candidate Recommendation.
Resolved: 2010 Snapshot is 2007 Snapshot + Media Queries
box-ordinal-group also reorders stacking order; i.e. it reorders the box tree.Tentatively scheduled: March 7-9 (MTW) 2010 in Mountain View and June 1-3 (WTF) 2010 in Tokyo
clear is applied to a run-in, it applies to the run-in itself if it displays as a block, and it applies to the block the run-in runs into if it displays as an inline.Discussed Release Candidate criteria, what happens to tests that are wrong, making implementation reports, and how we are measuring test coverage of the spec.
Test suite RC scheduled for September 15th; test errors must be fixed before RC. Implementation reports due 1 month after RC publication.
Reviewed Rune's proposal for an @viewport rule to set the size of the inital containing block independently of the viewport itself.
Comments included
@page { size: ... }Resolved: CSS Device Adaptation added to charter at medium priority, Rune to edit along with someone from Apple.