We’ve updated the compatibility table for the Selectors module to include the latest version of the Konqueror browser. Konqueror supports even more selectors than we currently have on the table, so the table will be expanded further shortly.
Due to the fact that it’s passed all the previous testing stages, many CSS3 Selectors have already been implemented in modern web browsers; Mozilla, Opera, Safari and IE7 all recognise at least a few of them.
We’re putting together a table of levels of CSS3 Selectors support in browsers; it’s still early and the testing is by no means exhaustive, but it should act as a good guide for those who want to start to implement CSS3 in their web pages.
Hello one and all, I’m Nicholas Shanks and have been helping out behind the scenes. My role is to build up the corpus of basic information about CSS Level 3 and how it has been developed, the W3C and WHATWG, and how everything in CSS3 came to be there.
To this end my first page has now gone live, detailing the current progress of each and every CSS 3 module through the vetting process. It allows you to see at a glance which modules are considered more complete. I hope you find it useful!
[tags]css level 3 modules, css3 modules, w3c, whatwg[/tags]
Update: Please see the note at the end of this article.
A potentially useful feature of CSS3 is the @font-face rule, which allows the developer to specify a font for the page that may not already be on the client’s system. Until now, most web sites have been developed with a small list of ‘web safe’ fonts – tahoma, verdana, etc, which are native to most operating systems.
@font-face will allow the browser to download a font for rendering the page; a link is given to either a remote site or a folder on the local site which the browser will access, download, install and render, so the site can be viewed in the way the designer desired.
A new preview page has been added, for HSL values in the Color module. So far, only Mozilla-based browsers support this feature.
Update: Also added HSLA values; only supported in Firefox 3 pre-Alpha.
[tags]css3, hsl, hsla, firefox, mozilla[/tags]
Since i’ve started with my CSS3 preview pages, i’ve had the same question at least 10 times already: why do browsers prefix CSS3 features? It seems so weird, when both WebKit and Firefox have
border-radiusimplemented, you have to write two lines for it to work in both browsers.
The Opacity declaration sets how opaque an element is. An opacity value of 1 means the element is fully opaque; an opacity value of 0 means an element is not at all opaque, i.e. fully transparent.