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!
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.
The Internet Explorer team have released a list of all the CSS changes which have been introduced into IE7. As we’ve already shown there is now the beginning of CSS3 support, with a few selectors included.
Other than that, despite the many changes IE7 is still below the level of almost any other rival browser and is not recommended except to those who have no alternative.
We made CSS Mania, and even though our design is way from being the best design up there, i think it rocks being featured on there :) We owe rakaz a big thank you, since without the header he made, we would NEVER have been on there :)
With the money gathered by the links that appear on this page, i have been able to buy the domain css3.net. Don’t know what i’ll do with it yet, it forwards to this domain now. But i’d like to know from you guys: what would be a good thing to do with this domain?
He mostly talks up the new RSS features in IE7 (which should really push the standard into the big time), but the most interesting answer he gives is to the final question:
Is IE going to auto-update to IE7? I think that the first thing really is that we can’t really force it on users. That’s not our goal. We really do like to offer users choice. It is a different user interface, some people will be really jarred by that. I think that we certainly want to encourage everyone out there to, um, I do believe that we will offer it through Windows Update, but it won’t be an automatic silent update, certainly it won’t be like you come in one day and suddenly your computer’s running IE7 rather than IE6. Certainly we have to ask the user if they really want it. As nice as it would be to blast it onto everyone’s system I don’t think that can happen, so.
Which means that it will be offered as part of the Windows Update programme, but not downloaded automatically. Which means we’ll have to put up with IE6 for a long time yet, and full CSS3 implementation is a long way down the road.
The undersigned has a post about how he learns webdesign on his school in Denmark, and to be honest, it’s frightening me. Table layouts apparently are the way to go according to his teacher, and designs are made using Dreamweaver. Allthough CSS3 might be a way ahead, if webdesign students in Denmark are taught like that, i hope they read a lot on the side on how things should be done…
Windows users who want to see what Safari is all about will be interested to know that a new browser (provisionally called Swift) is in development, which uses the WebKit browsing engine for the first time on Windows. You can download a preview of Swift here; be warned, it is a very early release and so may be buggy. I installed it on my dev PC and it seems to be stable, however.
The WebKit engine is lightning fast at rendering pages, but it does still have a number of quirks when implementing some CSS3 Selectors. If you’re not worried about using development software, download Swift and play with it a little.
As you can see, we have a new header pic, and some of the link colors on the site changed. The new header pic was created by Niels Leenheer, a friend of mine who did some work for Mozilla as well. He’s a cool dude, and i want to thank him here for taking the time to make this header pic!
Update: Ok it was altered a bit more, and we added a favicon and changed some layout. Looks better now imho :)
Update 2: Altered the layout some more, i’d like to hear your opinions!
Konqueror leads the way in the implementation of the CSS3 Selectors module – in the testing I’ve performed so far, only the :checked pseudo-class doesn’t seem to work.
I’ve updated the compatibility table so you can see for yourself how advanced this remarkable browser is; it’s just a shame that less than 1% of internet users choose it as their main navigator.