CSS WG Blog – Resolutions 2007-09 Beijing Part I: CSS2.1 and CSS Validator

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.

Resolutions 2007-09 Beijing Part I: CSS2.1 and CSS Validator

By fantasai September 24, 2007 (Permalink)
Categories: resolutions

The CSS Working Group has about three face-to-face meetings a year. This September we had one in Beijing. Since our face-to-face meetings are approximately 24 hours of solid discussion (split across three days), I’m going to break the resolutions reports up by topic.

Margin Collapsing (CSS2.1)

RESOLVED

Tentative Resolution: In CSS2.1 section 8.3.1 bullet 6 subbullet 2, change “non-zero top border” to “non-zero bottom border” pending Hixie’s ok. Recorded as issue #6.

CSS2.1 Test Suite Status Report

Status

We already have agreement on the test format.
HP has started contributing tests.
Microsoft wants to contribute tests, but is stuck waiting for the lawyers.

Other notes

The test suite would benefit from a way for anyone to run tests and contribute to their browser’s pass-fail report.
For testing open-ended multi-value properties, what should be the testing limit? Settled on test author assuming “reasonable” limit, documenting that the tests assume a “reasonable” limit, and suggesting that the specific assumption used in a test can be put in the test assertion.

CSS Validator

RESOLVED

Validator should emit warnings, not errors, for profile mismatches.
(again) The default for validation should be all the properties that are in a draft the WG considers stable. Users may ask for a specific profile to be used instead.
The validator should not offer a CSS2 profile. Features in CSS2 that are not in CSS2.1 can be validated against the default profile, just as if they were in a CR-level draft.
The validator should no longer offer a CSS1 profile.

« Previous article Next article »