I'm very glad this subject has come up again. From what I can see there are TWO types of opacity and confusion is arising from what we are all calling opacity;
1.) There is the files own opacity (alpha channel). 2.) There is the browsers opacity rendering. In v3.3 google said they fixed IE opacity issues - but in my opinion they actually broke it. They made it so the browsers opacity (2) works but in doing so broke the files own alpha channel opacity (1). So now if you have a PNG with alpha on it, you will get a dirty black noise around the transparency. HOWEVER, you are able to set the image to 20/30/40% opacity etc. Personally I think thats a waste of time because the images look so incredibly bad its pointless displaying them at anything other than 0% opacity. Try reverting your test document to v3.2 of the API and see if that fixes the problem? At any rate, its very irritating to keep seeings google response that the problem is fixed when it clearly isn't. On May 3, 1:18 pm, Nghi Nguyen <[email protected]> wrote: > Someone has the same problem with > me:http://code.google.com/p/gmaps-api-issues/issues/detail?can=2&q=3275&;... -- You received this message because you are subscribed to the Google Groups "Google Maps JavaScript API v3" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-maps-js-api-v3?hl=en.
