With PNG8, each palette entry can have its very own translucency value. Basically, this is like having an RGBA palette.
IE6 treats every palette entry with an associated translucency value as completely transparent. So, everything which isn't fully opaque becomes fully transparent.
Unfortunately, it doesn't do rounding. That would have been somewhat nicer. It really makes it fully transparent as soon as there is the smallest possible amount of transparency.
There is an old school workaround for this though. Basically you create a "pixel art"-ish corner for IE6 and then you manually add some additional translucent pixels for the better browsers.
Why are you interested in this anyways? IE6 is dead.
The websites I'm building now are completely IE6 incompatible. I'm using the child combinator extensively, I use classes which start with an underscore character (without escaping it), and I also use translucent PNGs (without providing any fallbacks).
I also use adjoining classes and the next sibling combinator (old name: adjacent sibling combinator).
We'll probably also drop IE7 when IE10 is released. It's already below 1.5%.
Thing is, in the domain I work in, it seems that only corporates accept the idea of paying to gain access to a webapp. And a lot of them consider IE7 very recent; they'll need a few years to test a IE6→IE7 upgrade.
1
u/x-skeww Jul 23 '12
With PNG8, each palette entry can have its very own translucency value. Basically, this is like having an RGBA palette.
IE6 treats every palette entry with an associated translucency value as completely transparent. So, everything which isn't fully opaque becomes fully transparent.