In what seems like a relentless update/upgrade competition with the "other" browsers, Firefox 11 is NOW not playing nice with Shockwave Flash, or is it vice-versa. This didn't start happening until I "upgraded" to Firefox 11.0
YES, I've updated ALL the plugins (Who invented this plug-in hassle, anyway?), as is ABSOLUTELY required whenever Firefox goes through one of its myriad of updates/upgrades. I've uninstalled/reinstalled Flash, and my WinXP Pro is up-to-date. I haven't experienced this torrential headache with IE 8.0, OR before F-11.
Is there a Firefox 18.104.22.168.2.3.4 patch in-the-works, or do I have to consider one of the "others"? HELP ME!
Hello I really need your help. Tuesday I downloaded the new version of Adobe Flash Player for IE 22.214.171.124 and the plugin for Firefox and then the problems began.
Every time when I read a video or listen to music (youtube, dailymotion, musicMe, Grooveshark etc ...) and I let my scroll the mouse wheel, this jerk I can not do anything and firefox freezes. Then I looked on IE and I found that the problem was also present but less than firefox.
I already uninstall and reinstall Adobe Flash player three times but the problem is still there. What to do?
Thanks Swarnava, but if you'll READ my problem, I've ALREADY done all that; it was the actual upgrade TO Firefox 11 - THAN having to update Flash afterwards - that is causing the problem.
I don't think I'm the only one experiencing this issue. I've been using Firefox since 1.0, and version 11 has been a headache.
Good luck zalout, because I believe Mozilla (i.e. Firefox) MIGHT be aware of the minor "problem", they just need to acknowledge that there IS a problem and do something before we all UNINSTALL in droves.
There IS a problem with Firefox 11 and Flash 11 playing nice together; it's just WHO'S problem is it. Works fine with IE 8 ...
Rouser thank you good luck to you too, could someone please help, this is really painful this problem. I even contacted Adobe but he did not answer.
There's not going to be a solution to this problem, since apparently the problem doesn't exist.
We'll just have to wait for the next Firefox update (plus all the plugin updates that go along with it) before this issue "mysteriously" disappears. Cross your fingers ...