Re: Internet Explorer Implementation Report

John Jansen wrote:

> > Hi John,
> > 
> > > Apologies for not sending this announcement to the public list sooner.
> > > Our Implementation is up on the site[1] based on our publicly
> > > available Beta.
> > >
> > > (HTML and xHTML tests):
> > >
> > > Pass: 18960 — 97.40%
> > >
> > > Fail: 383 — 1.97%
> > >
> > > Invalid: 60 — 0.31%
> > >
> > > Skip: 63 — 0.32%
> > >
> > > As with others, we expect to continue to improve our results over time
> > > and will continue to update our IR as the suite changes as well.
> > 
> > Was this done with a publicly available IE9 beta or with an unreleased
> > version?
> > IE claims passing all font-family-name-* tests which I can't reproduce.
> > 
> 
> It was with the publicly released beta that shipped on Sept 15th. Did you remember to install the ahem font?

The font-family-name-* tests are my tests, they use the CSSTest fonts
not Ahem. Among those tests is an explicit check for font family name
matching using GDI which the latest IE9 beta appears to still use for
font family lookups.  GDI allows matching on names other than the font
family and this won't work across platforms (ditto for Postscript name
lookups in Webkit).  If the tested version of IE9 uses the
FindFamilyName method of a IDWriteFontCollection system font object,
then everything will match correctly.

Here's an example of what I'm talking about, IE matches "Arial Bold" and
Webkit/Mac matches "ArialMT-Bold" as *family* names:

  http://people.mozilla.org/~jdaggett/tests/arialvariations.html

I constructed explicit checks for these which is why I'm puzzled how all
these tests passed.  Maybe they were run without the CSSTest fonts
installed?

Cheers,

John

Received on Wednesday, 27 October 2010 03:49:55 UTC