CSS is getting closer and closer to being correctly implemented by all browsers (IE8 passed the acid test) but life as a web developer is not getting easier. If you thought Safari on Windows was “cool”, web developers around the world shed a tear. Just because a software is labeled cross platform doesn’t mean that it behaves the same on all platforms. I am not sure if my latest gripe lies with the Firefox browser or the flash player but there is a bug in Firefox for Mac where if html content is overlayed Flash content the html content flickers. The fix? get rid of any flash elements from under html content (by masking out the content when mac firefox is detected or hiding the layers)
Remember the browsers that you support is not determined solely by the site audience but also by whatever the hell your boss/client uses.
John Dowdell
January 25th, 2008
I can’t tell, from what you wrote, if you know of WMODE. Browsers have been pretty good about it lately, but there’s always a chance for regression in a browser build.
jd/adobe
akeemphilbert
January 25th, 2008
Yes wmode transparent is being set (works as expected in windows browsers IE et al. and mac safari). It just fubars in mac firefox. Also wmode isn’t kosher on linux firefox as well (I only got that one because I run nix at home.) It not a big deal yet but as more and more clients get macs its slowly going to become a pain to deal with inconsistencies (performance difference etc).
John Dowdell
January 25th, 2008
I hear you. But, hmm, I’m in Firefox/Mac 2.0.0.9 right now, and I’m able to see transparency in the following example. Can your browser view this background-transparency too?
http://www.adobe.com/go/14201
That “background transparency” should be the same mechanism as CSS layering, but just in case, here are three layering-specific tests, which seem to work in my copy of Firefox/Mac:
http://veerle.duoh.com/index.php/blog/comments/experimenting_with_flash_content_and_z_index/
Can your browser view these examples? This could help us figure out whether the symptom is dependent on browser/Player version, or whether it’s a specific way of handling the markup that’s at cause.
jd/adobe