User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:126.96.36.199) Gecko/2008070206 Firefox/3.0.1 Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:188.8.131.52) Gecko/2008070206 Firefox/3.0.1 While running shockwave content containing interactive content (such as buttons, sliders, etc.) parts of it will become invisible (or transparent) and the background color will "cover" the shockwave content, so it does not display in a reasonable fashion. Reproducible: Always Steps to Reproduce: 1. Load shockwave content that is interactive. Click on buttons, checkboxes, etc. Click on the html page (a non-shockwave region). 2. Resize the window of the browser. The content will reappear. Actual Results: Portions of the content become invisible. Just the background color appears. Expected Results: Shockwave content should display correctly. This is easily reproducible on both OSX (10.5) and the current release of Vista on a PC, and has been seen by other Shockwave developers. I recall seeing this problem when 2.0 was first released (but can't be 100% sure about that), which was fixed in a point release. This problem is still present in the latest nightly build. More content can be observed at explorelearning.com (you can view anything for up to 5 minutes).
Note: Vastly harder to reproduce on Windows.
I can reproduce this in FF 3.0.1 on OS X (10.5.4), but not on Windows (XP). In both cases I installed and tested with the current version (11.0.0r465 on OS X and 11.0 on Windows) of the Shockwave plugin (from Adobe). I can't reproduce this in FF 2 on either OS X or Windows XP. Since comment #0 says this can be seen on Windows, marking "All" ... at least for the time being.
Although I've only done limited testing, this bug may have been fixed in 3.6.0 that was released earlier today.
Looks like the problem is not entirely gone yet. Seems much better than the entire 3.0-3.5.x line though.
Shockwave 184.108.40.2069 was released, and it is reported that this bug is fixed. Can this bug be closed?
Yes, the problem went away with FF 3.6+ combined with SW 220.127.116.119+. I'll mark this as resolved, although I'm not sure if I really have "power" for something like that. At least it got fixed ;)
for plugins, if the vendor claims to have fixed the bug then yes we're happy w/ FIXED, and if a reporter or someone else can confirm that the problem is resolved, then we're happy w/ VERIFIED. Thanks for confirming :)