CSS3

You should mention the format specifier of src, unicode-range and panose-1 properties as these are fairly critical to the font's behaviour. You also are not particularly clear about the local() parameter. This takes fonts from a specifc path on the user's machine, e.g. local(/Library/Fonts/华文仿宋.ttf) is the same as url(file:/Library/Fonts/华文仿宋.ttf). I'm not sure what local(../foo) would do, as I have no idea what working directory the browser would be set to! Presumably /Applications/Safari.app/Contents/MacOS for Safari. Posted to " @font-face: fonts the way you want them " by Nicholas Shanks June 23rd, 2006

As have I, indeed I first implemented this as an algorithmic way of providing the CSS3 font-outline property for fonts that don't come with an Outline face. See http://bugs.webkit.org/show_bug.cgi?id=9475 Posted to " New text declarations in Webkit " by Nicholas Shanks January 1st, 2007

Some more stats from TheCounter: (12% for IE7) http://www.thecounter.com/stats/2006/December/browser.php Posted to " The rise of IE7 " by Nicholas Shanks January 9th, 2007

But rises to 19% for this month! http://www.thecounter.com/stats/2007/January/browser.php Posted to " The rise of IE7 " by Nicholas Shanks January 9th, 2007

David says: I think once every year is just right. Time for you to get to know the new version properly. I disagree with this, and believe a much more frequent upgrade cycle (dependant on the development pace of your browser) would prevent you from ever having to ‘get used to’ any changes. They would creep in one at a time and you would be able to take them on board much more easily. I, for example, update my browser's rendering engine to the latest code every 2 to 3 days. Areas such as SVG and CSS support have usually had at least one bug fix or new feature I'll notice in that time. Other benefits that are harder to perceive include better and faster JavaScript support. Perhaps a website I visit wouldn't have worked in an older version of my browser, but when I visit it works fine and I never even notice :-) Posted to " How often should browsers upgrade? " by Nicholas Shanks January 12th, 2007

Ian commented that it was done in an IRC chat room about 4 hours ago, I expect an official announcement to be made within 24 hours. The most recent WebKit nightly gets 64%, a significant improvement on the released Safari 3 (which gets 40% on the Mac side too). Posted to " Acid3 browser test completed, available now " by Nicholas Shanks January 30th, 2008

Regarding the 64/36 number: Tests number 65 and onwards are commented in a way that lead me to believe they were sourced from a competition for contributions. I see now that not all are attributed to third parties. My apologies. Posted to " Acid3 browser test completed, available now " by Nicholas Shanks January 30th, 2008

@brad: dynamic style changes (user or javascript) when used with the sibling selectors are known buggy issues. they work fine otherwise. in fact IIRC they were partuially fixed a few days ago (fixed in that if you use one sibling selector it now updates, but two or more is still broken). Posted to " Safari 3.1 pushes CSS3 support forward " by Nicholas Shanks March 26th, 2008

Yes. In fact, @font-face is designed to work best with Unicode fonts and Unicode text (both UTF-8 and UTF-16). (Rather than, for example, fonts using custom encodings.) Posted to " Mozilla implements @font-face " by Nicholas Shanks July 30th, 2009

Konqueror now uses WebKit and has dumped its own KHTML branch. Additionally, WebKit has always parsed both the -webkit- and -khtml- prefixes anyway. http://arstechnica.com/open-source/news/2007/07/t... Posted to " Even more Konqueror CSS3 goodness! " by Nicholas Shanks August 7th, 2010