It’s all gone a bit quiet round here… sorry about that, but there’s not a lot of movement on CSS3, and I know the authors here are quite busy personally.
Anyway, potentially big news is that the WHATWG are asking for developer feedback on HTML5.
I’m still wading through the document, but of what I’ve read so far, of most interest to CSS fanatics will be a group of new, semantic tags; for example
Of course these aren’t directly related to CSS3, but it should help save a lot of classes, ids and tag soup if implemented – and that’s the key. Even if it turns into a recommendation, how long until HTML5 is supported in IE – if at all. Many questions, many variables; but stay positive, and give your opinion.
Boys and girls, dear readers, read this article I wrote for an SEO contest, and help me create as much buzz about it as possible. If you help me win the SEO scholarship contest I wrote this for, I can build even more great sites for your entertainment :). So read all about how to run your sites like you’d run a pub.
Last week we unveiled the CSS selector test over at css3.info. The test consists of over several hundred separate test cases, each designed to test a certain aspect of the compatibility of your browser with the CSS selector standards. Today we are going to expand the number of test cases to 578.
The new tests have a large impact of the results. There are quite a few browsers that used to pass with the old test cases, but fail with the new test cases. Generally we added test cases for the following situations:
:emptyselector. It only matches elements without any children. If you dynamically add a new child it should not longer match that particular element.
- White space in attribute selectors: There are four different ways an attribute selector could be written:
[attribute = value]. We now test if your browser supports all of these variants.
- Case sensitivity of the value in attribute selectors: The previous version of the test contained a test case for determining if the value of an attribute selector was compared in a case-insensitive way. However this was not complete. We only tested the
alignattribute – which should be treated in a case-insensitive way. Only Konqueror failed this test. But there are also a lot of other attributes which should be tested in a case-sensitive way. Now almost every browser fails this test. More information about this case-sensitivity can be found on rakaz.nl: CSS selector bugs: Case sensitivity
We also changed the way results are reported. Instead of just showing whether a selector failed or passed, we now detect if the selector is fully supported, buggy, or not supported at all. This should give all of us a better idea about the state of the compatibility of each browser.
Browser Version Supported Buggy Unsupported No. tests passed Internet Explorer 6 10 1 32 276 Internet Explorer 7 RC 1 13 4 26 330 Opera 8.5.4 18 3 22 317 Safari 2.0.4 21 7 15 336 Firefox 1.0.8 24 9 10 352 Opera 9.0.2 25 3 15 346 Safari r16925 25 9 9 355 Firefox 220.127.116.11 26 10 7 357 Konqueror 3.5.4 37 6 0 570
Bert Bos announced on the www-style mailinglist that the CSS3 Paged Media module Working Draft (WD) is now in Last call status, which means that it will probably advance to being a Candidate Recommendation (CR), according to the W3C development process.
KHTML, the Konqueror rendering engine, has received another upgrade – and with it, more implementation of the still-officially unannounced CSS3!
According to the release notes, KHTML 3.5.5 now has support for the HSV/HSVA color values. I must confess to being a little baffled by this; the CSS3 color module names HSL/HSLA values (of which HSL is supported), but not HSV/HSVA. Perhaps someone more au fait with colours could help me out on this one.
Also now supported, apparently, is the outline-offset property – which does exactly what it says; offsets the outline around a page element.
Please bear in mind I haven’t tested these, yet.
And don’t forget out the blogpost Niels made about the CSS selector bugs he discovered.
The latest version of the Konqueror browser, 3.5.4, supports more CSS3 declarations.
See the full list of changes for the latest release here.
I’ve said it before, but it’s really a shame that probably less than 0.1% of internet users choose Konqueror.
Update: I’ve just seen that Konqueror has also implemented the :checked selector, making it the first browser to support every CSS3 selector. In the last month, 0.48% of this site’s visitors used Konqueror – and I suspect quite a few times it was me, testing.
Eric Meyer, in one of his latest posts in the W3C change series, proposes quite a radical change for the W3C: full independence.
The article is well worth a read, coming from one of the people with the most insight in to W3C operations, and I agree with him: it’s a very good idea. Let’s hope more people think of it that way, and let it happen!
So it’s been quite a while, and i should have ended the summer contest almost a complete month ago, but due to extreme business on my side, with a new born son and other stuff, i didn’t get around to it. But I have finally come to it, and here it is:
The CSS3 summer contest winners!
- The fifth prize goes to Mauricio Samy Silva for the complete selectors explanation he made that i have yet to work in to the site.
- The fourth prize goes to Peter Gasston, fellow blogger on this blog, for his blogposts and other great work he did for this site.
- The third prize goes to Mihai Sucan, for his excellent speech preview.
- The second prize goes to Mauricio Samy Silva, for the attribute selectors preview he made.
So, people, please contact me with the name and email address you want your prizes to be registered to, and i’ll get them to you!!
A couple of links with some relevancy to CSS3:
CSS Shortcomings: Why CSS2 isn’t perfect for layout, and what’s in the CSS3 spec to correct that.
IE7: Old Bugs for New: Microsoft’s next browser won’t be helping to push the web forward; it’s so full of bugs that even current pages may not display properly.