Firefox 3 + Adblock = disaster
I installed Firefox 3 in my Mac yesterday and I'm liking it better than version 2. It seems to be faster and it solved some problems I was having.
I discovered later that one extension I have installed, Adblock, was blocking *ALL* Flash content. I was using SWFObject's dynamic embed mechanism, so I am not even sure how it was blocking that, but it was.
The solution: completely disable Adblock. By the way, you need to disable the extension, not Adblock's disable feature, because even when disabled, it wouldn't show Flash content. There are tons of comments describing this problem in the extension's page at Mozilla, so I hope they fix it soon.
So that's regarding Adblock. But I should also add to the title Firefox + Flex = disaster, because I am running into some very strange problems with the Flex app I was trying to test. I saw the problem on other apps as well. If I have some elements in the screen that are clickable, and I click on them, I would see the html background as a square in what it looks like the Flash player redraw regions, which are approximately the size of the element I was clicking on. That would make the square flicker for a second, then I would see the normal content. It's as if the redraw region would become transparent for a second, then back to normal. Very annoying. Normal buttons work fine. Has anyone seen this?
i had the same problem, even though it wasn't the firefox update, but the upgrade to flash player 10 beta.
the problem i had was that some older versions of adblock don't automatically get updated (5.x). if you manually update to the most recent 7.x version, all should be well.
if not, then i don't know what the problem could be ;D
btw, nice work on the Mate framework! i'm starting to get into it and love it so far =D
I was using Flash Player 9.0.115. I'll check if I can upgrade Adblock and see any difference.
I'm glad you like Mate!
flobster and Wladimir,
I was using Adblock, not Adblock Plus. I may try Adblock Plus instead.
to faslse worked for me
The second problem you mention it is a problem for FF3 MAC.
I've been digging into this blink for the last two days always thinking that was a very specific bug in the SWFAdress but my surprise was when I create a project without using the SWFAddress and using only a couple of ExternalInterface calls.
Here there is an example, the grey button on the left calls an alert with a timeout and there is not a problem, the second button calls an alert straight away and the whole movie goes 'bananas' and the red button on the right calls a simple scrollTo(0,150) using ExternalInterface.call and makes everything to dissapear apart of some graphics.
yeah, the problem came down to SWFAddress. There were some people talking about in the forums. The only work around that somewhat worked was to add a delay.
But now you are saying that the real problem is in ExternalInterface, which SWFAddress uses... I wonder whose bug this is, I really don't like the workaround.
I had the same problem, and use the same solution.
But after deleting few extensions more, FF works much better ;)
Make sure to disable/delete unused extension for a better performance.
Adblock blocking all **unsigned** swf objects? Maybe even signed ones? Oh, what can I say? That's why we love that addon: to get rid of all the crap :)
The common example is that a user blocks "http://download.macromedia.com/pub/shockwave/cabs/flash/*" on one site after seeing an annoying ad and now any other flash that matches that address (which is very common) is now blocked for the user everywhere.
Other than for videos, all applications of flash tend to be annoying for users as it is.