First, here’s another table showing CSS support in web browsers, including CSS3 declarations.
Unfortunately the author only seems to have access to browsers that run in Windows, so it’s not as complete as it could be. Interesting, nonetheless.
Update: I stand corrected. There are options to choose which browsers display in the table, which makes it very useful.
We’ve been focussing a lot on what we will gain from CSS3, but of course we will lose some things too; namely, some of the CSS tricks we’ve come to rely on over the past few years.
I’m thinking about some of the great techniques that have been developed to stylise the web, like the ‘sliding doors’ technique, for example. It’s a simple and elegant way to style your navigation lists, but it will be made redundant either by border-radius or multiple backgrounds (or a combination of the two).
As you might have seen, we have moved the blog from /blog/ to the main domain, since the homepage wasn’t exactly useful anyway. In the process we have moved some pages that were static into WordPress, and we will be doing that for most other pages as well in the coming weeks. If you see glitches, feel free to mail us, we’ll try and fix it.
Mozilla released Gran Paradiso alpha 2, which is what will become Firefox 3. Running it through the CSS selectors testsuite shows there’s been a few improvements. It passed 32 out of the 43 selectors. Only 4 are buggy and 7 unsupported. That’s not a big improvement over Firefox 220.127.116.11, as that browser passes 26 of the 43, with 10 buggy and the same number of unsupported selectors. It looks like they’ve debugged issues with their attribute selectors so far, but this is only an alpha so there’s likely lots of improvements yet to come.
Sometimes it’s difficult to figure out why we might need some aspects of CSS3. Like why would anyone ever need
:not()? After all, it’s like it works on elements we don’t care to style. Why would we need that?
Recently I posted about Konqueror 3.5.6 and said:
It really is a shame that only a tiny proportion of web users have access to this excellent browser.
That comment was picked up by this blogger who responded:
Virtually every web user can use Konqueror. All they would need to do is install an operating system like Linux, FreeBSD, OpenBSD, NetBSD, Solaris, or Mac OS X.
The future of webdesign part II
In part two of the interview series we’ve dubbed “the future of webdesign”, we have an interview with Veerle Pieters, one of the best webdesigners on this planet, and a lovely lady as well!
Check it out:
Andy Clarke’s Transcending CSS is a book that anyone involved with client-side web development should read.
For web designers who know some code there is plenty of forward thinking material about the importance of semantic HTML; for coders with an eye for design there is lots of food for thought about colour, style and inspiration; for everyone, there are some genuinely innovative tips on using CSS to tie it all together.
Are you dying to play with some of those CSS3 features that Opera‘s implementing, or is it just me? Well, it turns out there’s a way we can play with them already.
There’s a little program that takes XML+CSS and turns it into PDF‘s. It’s called PrinceXML, which already supports all those wonderful little CSS3 selectors the Opera folks are making us salivate over. The only downside here, is that PrinceXML isn’t a web browser, but a printing program. It’s still very useful and gives us a good playground to practice on.
Here’s a partial list of CSS3 selectors PrinceXML supports:
E ~ F