I do an optimized build with Direct Draw enabled. On 95, any area with "opacity" doesn't work, but on NT, it does. If I recompile without direct draw, the problem goes away. Both NT and 95 displays are 16bit color.

This demo (URL) looks best at 800x600, by the way.

Putting on ss: radar.

Currently I don't think the build team is building with the direct draw environment variable turned on, so I don't think this should be a ss:. Additionally, no pages on the net use the opacity: CSS property since we just invented it a few weeks ago, so we can handle this pretty well I think. Jan, I'll leave it up to you to remove the "ss:" if you think that's OK.

what he said. this is not a stop-ship item.

Setting all current Open/Normal to M4.

assigning ChrisD as QA assigned

kevin we need to talk some more about direct draw support and what the deal is here... x3178.

Moving to M8

Moving to M11

Moving to M12

Moving to M13

Moving to M15

Moving to M18

This bug has been marked "future" because the original netscape engineer working on this is over-burdened. If you feel this is an error, that you or another known resource will be working on this bug,or if it blocks your work in some way -- please attach your concern to the bug for reconsideration.

Since you mention that both are 16bit color, I will add that there are sometimes problems with 565 16-bit and 555 15-bit. I have had problems with this with other programs. Perhaps the GFX people might understand this. The program that had this problem was Amaya from the W3C where colors would look wrong.

The mentioned option no longer exists.