Linked by Thom Holwerda on Wed 15th Sep 2010 19:14 UTC
Internet Explorer After several months and preview releases, Microsoft has finally lifted the curtain for the Windows Explorer 9 beta release. Internet Explorer 9 is Microsoft's attempt at not just catching up to the competition, but at actually surpassing them. Since enough sites will be focusing on just how many nanoseconds faster or slower the beta is compared to the competition, I'll talk a little about the new minimalist interface.
Thread beginning with comment 441301
To view parent comment, click here.
To read all comments associated with this story, please click here.
Member since:

That article talks about rendering text at "small sizes", but even large sized text isn't rendered correctly.
The IE9 "Welcome" screen itself:

The big blue "welcome to a more beautiful web" text is jaggy, particularly noticeable on the "e" and "a" characters, but almost all of the characters are bad. Zooming only enhances the jaggies.

Yet if I go to the IE9 Test page ( (the one that the IE9 Platform Preview has been using)), the text looks fine, both in general and in the various DirectWrite and WebFont tests (the rendering, animation, scrolling, and zooming is all fine). I assume that DirectWrite has trouble with certain fonts, but it's weird that the IE9 Welcome page would use one of the problematic fonts.

Anyway, the IE blog says that they're aware of the text rendering issues and will address them in an update to the beta.

Reply Parent Score: 2

nt_jerkface Member since:

They are trying to downplay the situation in that article but it is true that it is more of a problem at smaller sizes.

On my monitor that title just looks a bit thin in IE9 but the letters look fine. The fonts in this thread are what look a little fuzzy.

This is the WPF 4.0 fix:

and if you look in the comments you can see that there are still complaints. It's a huge improvement from the original WPF release though. I've seen quite a few comments on places like stackoverflow where .net developers have been avoiding WPF for this reason.

It really breaks down to favoring accuracy over readability with the assumption that monitors would have higher DPIs by now. Firefox uses direct2d for hardware acceleration and is running into the same problem:

Edited 2010-09-16 16:57 UTC

Reply Parent Score: 2

Neolander Member since:

As you probably understand microsoft's internal organization better than me, could you explain me why Microsoft doesn't simply push an update to WPF that automatically switches font rendering to display mode under 15 pt fonts and ideal mode above 15 pt ? Couldn't that be a simple and efficient fix while screens improve ?

Reply Parent Score: 2