He raises the point that not every internet user wants their browser upgraded every year, saying:
During the open mic session [at the Mix conference], someone said "please don't ship a browser every year – I can't handle that"… [There] are people who say, "I'm using an extranet in order to get my billing done and I'm scared. I really don't want browser changes because this is how I get paid".
Last month I did an audit on some websites I manage to see what kind of take-up IE7 had; the figure varied between 1% and 12% of total visitors. Now that Microsoft have placed the new browser into the automatic download programme, I decided to go back and revisit the stats again.
The Webkit project have announced support for a new range of CSS declarations, to be used for putting strokes around text. This strikes me as a little strange for two reasons:
I went through the logs of some of the sites I own or manage today, to see what kind of uptake there’s been for IE7. From ten sites, some business and some personal, the percentage of users varies between 1% and 12% using IE7.
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 22.214.171.124 26 10 7 357 Konqueror 3.5.4 37 6 0 570
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.
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.
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.