IE7 vs. DXTransform or How bugs become features

Information for consideration.
Returning to the topic of text rendering in browsers , I wanted to touch on the topic of IE7 problems in combination with DXTransform-filters ; the most common one sometimes encounters is filter: opacity (), for example. (my translation)

Hello again, this is Peter Gurevich, I’m the IE project manager for the ClearType part (besides what I can read about on my blog). Today I want to draw your attention to the question of the interaction of DXTransforms and ClearType, as well as to tell what we have done to improve the readability of the text in IE.

During our tests, we noticed that the DXTransform is sometimes applied to elements that contain text (which is now rendered with ClearType). Just as our users noticed, the text smoothed by ClearType looks too blurry - unfortunately, these two technologies do not fit well. This is due to the fact that the transformations used in the DXTransform do not take into account the spatial nature of ClearType.

To ensure good readability of the text in IE, in the release candidate we decided to disable ClearType for all elements to which the DXTransform is applied. We will draw the text in these elements unsmoothed, so that it is better read. The rest of the text on the page will be displayed via ClearType. This explains why some (or a bit more) sites will show the text unchecked.

Further comments in the comments. The developer suffers:

This problem can be observed in other cases (bold text or PNG with translucency, for example). They all have the same solution: you need to set the background color. As long as this is not an acceptable solution at all times, this is at least what the developers use when they have to reckon with IE in order to create a page more or less similar to what is needed. And with these changes, this solution ceases to be a good one. This means that we can either have a beautiful text or transparency, but everything will not get right away. This is unacceptable. And until the problem is solved everywhere, we get another crutch in addition to all the others that create so many problems with the support of IE. Either repair or leave as is, but do not create another surprise, which can not be controlled. After all, you can enter for example a filter ("-ms-text-smoothing" or something like that). You can even set its default value to 'none', if you really need it. But at least it will give developers the opportunity to fix the bug without losing functionality.

The usual user suffers:

It is unfortunate that MS simply did not make an OPTION that turned it on or off. I prefer it to be included everywhere, on all sites, no matter if the text is blurred or not.

And finally, the worst thing:

Judging by the reviews: 185407, in IE7 it is not repaired. They are almost done, and RC1 seems to be what we will see eventually. I am very upset that they decided to abandon ClearType. I have never seen such distortions, it would be better to leave ClearType turned on everywhere, or off everywhere.

Well, for example, how the site breaks, if the developer has crooked hands to abuse these filters.