Web authors' contributions to CSS 2.1 test suite

If you want to submit testcases to the CSS 2.1 test suite...

Contact: css21testsuite-submissions (at) gtalbot [dot] org

Useful documents to consult

• CSS Working Group Wiki: Testing
• CSS2.1 Test Case Authoring Guidelines
• CSS 2.1 Test format guidelines

If your testcase does not comply with such guidelines or such format, I will help and assist you.

Where to search for possible duplicates?

Among testcases already submitted to CSS 2.1 test suite by various parties and also in already approved testcases

Signing up the W3C form

If you want to be credited for the testcases you submit, then you will have to eventually sign up the W3C's license grant form so that you give W3C permission to distribute your contributions. Read more info on How to License Your Contribution. I will assist you if you need help on this issue.

Frequently Asked Questions

Do you accept testcases which target specific browser bugs?

Yes, absolutely! A testcase which is passed by all current mainstream browsers is less helpful, less useful for all mainstream browser development teams than one that is failed by 1 or by a few of the most recent browser versions (eg Internet Explorer 8, Firefox 3.6.8, Opera 10.61, Safari 5.0.1, Chrome 5.0.375.126, Konqueror 4.5) coming from the current mainstream browser manufacturers (Microsoft, Mozilla, Opera, Apple, Google, KDE). The number 1 purpose of the CSS2.1 test suite is to help achieve interoperable implementations of CSS 2.1 among web browsers and web-capable softwares. So, identifying testcases which are not properly supported or which are not correctly implemented in the latest stable version of a mainstream browser is helpful and relevant. A failure in a particular testcase will inform the involved browser manufacturer development team about it.

There are many positive aspects to submitting testcases which fail in recently released browser versions (e.g. Internet Explorer 8, Firefox 3.6.8, Opera 10.61, Safari 5.0.1, Chrome 5.0.375.126, Konqueror 4.5, etc). Still today, I would say that 50% of all questions asked in web authoring forum discussions newsgroups or in BBS are about browser incompatibilites (or suspected browser bugs) when rendering a particular webpage (markup and CSS) code.

Which types of testcases have not been created, submitted a lot so far? Which types of testcases are you looking for?

4 types of testcases.

1. shrink-to-fit width testcases: they can involve floated elements, non-replaced inline-block elements and non-replaced absolutely positioned elements
2. Testcases involving relative units (which are so important to achieve scalable design): e.g. padding-left: 20%; max-width: 10em; etc.
3. Testcases involving the inherit keyword value for properties which do not by default inherit from their parent or from their containing block: e.g. max-height: inherit; overflow: inherit; etc.
4. Composite testcases: testcases which may combine a few (2-3) or several (4-6) properties in realistic webpage scenario.

What should I do if I have a few testcases to submit?

First, make sure your testcases use valid markup code and use a XHTML 1.0 doctype declaration referencing to strict DTD. Then, make sure the pass and fail conditions of your testcases are clear and easy to figure out. Then, contact me.

What should I do if I have several testcases to submit?

First, read carefully the Contributing to the CSS Test Suites. Then upload your testcases on an accessible website. Creating a webpage (an index.html page) that can act as a table of contents linking to your testcases will be helpful. Then subscribe to the public-css-testsuite mailing list and announce that you have testcases to submit, to be reviewed and that you want to participate in the project.

When should I sign up that W3C's license grant form?

When you have submitted at least 1 testcase that has been reviewed or that is considered as acceptable for CSS 2.1 test suite.