"A few months back I submitted the smallest speck of an idea for a talk I was hoping to present at Over The Air in London. Having presented at Over The Air before I assumed my experiences this time around would more or less be the same - a chance to bounce a few of my recent thoughts off two-dozen or so UK developers.
To suggest that my assumption was wrong would in-fact be a massive understatement...
Three weeks later, the dust is still settling on the 90,000 140,000 presentation views, hundreds of tweets, and multitude of conversations, and I finally have time to provide the presentation with a much-needed introduction."
(Bryan Rieger)
Fig.1 "Rethinking the Mobile Web" by Yiibu
"We built SuperPreview to simplify the process of testing and debugging layout issues across different web browsers and platforms. You can view your pages in multiple browsers simultaneously or view how a page renders in a browser and compare it to a comp or mock-up image of a page.
...
SuperPreview will be included as part of a future version of Expression Web. The final feature set and its availability have not been announced. The SuperPreview demo shown at the MIX09 conference was a technology preview and not a product announcement. However, because we'd like to get feedback on this technology and on its implementation, we have announced a beta version of SuperPreview for Internet Explorer. This free download will allow you to compare renderings of IE6 with whatever other version of IE you have installed on your machine. If you have installed IE8, you'll be able to compare IE6, IE8 and IE8 running in IE7 compatibility mode, side-by-side. The final 'shipping' version of SuperPreview for Internet Explorer will continue to be available for free. The Expression Web team hopes that it will be useful in helping to make the process of developing web pages for IE (and in general), faster and easier."
(Microsoft, 2009)
"A short while ago, Mozilla announced that Firefox 3.1 will, along with Safari which already does, support the @font-face mechanism for linking to online TrueType fonts. Internet Explorer already supports (and has done so for years) @font-face font linking, but here's the catch, not to TrueType fonts - only to EOT font files. EOT, now a proposed W3C specification, incorporates anti copying technology, helping to assuage the fears of font foundries that font linking in browsers would unleash a wave of unlicensed copying of their fonts. Chris Wilson, Platform Architect for Internet Explorer has made it clear that he's strongly opposed to simple font linking
we (Microsoft) should NOT support direct TTF/OTF embedding, unless 1) there is some check that the font intended that use to be allowed, which I don't think there currently is (as it needs to refer to the license agreement), AND 2) other browsers also implement a system that actually ENABLES commercial fonts - those that are allowed to be embedded, but cannot be legally placed directly on a server - to be used
So, is this a return to the stalemate of the 1990s, when both the major browsers supported font linking, only of a completely incompatible type? From a technical point of view, no. Since the same mechanism, @font-face rules, is used to link to TrueType, EOT and other font formats, then it is quite simple to define multiple fonts, and the browser can use the font format it supports."
(John Allsopp, 19 October 2008)