Web authors' contributions to CSS 2.1 test suite

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

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

Useful documents to consult

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

Where to search for possible duplicates?

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

Signing up the W3C form

If you want to be credited for the tests 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 tests which target specific browsers or browser bugs?

Yes, absolutely! A test 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 (e.g. Internet Explorer 11.0.9, Firefox 30, Opera 12.17, Safari 7.1, Chrome 35.0.1916.153, Konqueror 4.13.3) 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, having tests which fail in the latest stable version of mainstream browsers is helpful and relevant. Failures in particular tests will inform the involved browser manufacturer development team about it.

There are many positive aspects to submitting tests which fail in recently released browser versions (e.g. Internet Explorer 11.0.9, Firefox 30, Opera 12.17, Safari 7.1, Chrome 35.0.1916.153, Konqueror 4.13.3). 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 tests have not been created, submitted a lot so far? Which types of tests are you looking for?

3 types of tests.

  1. Testcases involving relative units (which are so important to achieve scalable design): e.g. padding-left: 20%; max-width: 10em; etc.
  2. 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.
  3. Composite testcases: tests 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 tests to submit?

First, make sure your tests 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 tests are clear and easy to figure out. Then, contact me.

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

First, read carefully Contributing to the CSS Test Suites. Then upload your tests on an accessible website. Creating a webpage (an index.html page) that can act as a table of contents linking to your tests will be helpful. Then subscribe to the public- css-testsuite mailing list and announce that you have several tests 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 test that has been reviewed or that is considered as acceptable for CSS 2.1 test suite.

Valid HTML 4.01! CSS compliant Web standards project HTML Tidy