Comments on: jquery.flash v1.3.1 – Squashing IE-related bugs.

By: Matthew Clemmons

Matthew Clemmons — Mon, 26 Mar 2012 22:33:00 +0000

@Justin, great find right there. If anyone is having layering issues with jquery.flash in Chrome, this is the solution. As Justin points out, add “type” to “availparams” and set the “type” in your jQuery call.

By: Justin

Justin — Wed, 22 Feb 2012 11:11:00 +0000

Seemed to be having problems with transparent wmode in Chrome. I added “type” attribute with value set to “application/x-shockwave-flash” to non-ie output and all worked fine.

By: Stephen Belanger

Stephen Belanger — Wed, 04 May 2011 02:14:00 +0000

Good to know.

By: PaulCormier

PaulCormier — Wed, 04 May 2011 01:15:00 +0000

I did some more testing. It appears to be bug in FireFox. IE & Chrome do not exhibit this behavior. See: https://bugzilla.mozilla.org/show_bug.cgi?id=654241

By: Stephen Belanger

Stephen Belanger — Wed, 04 May 2011 00:00:00 +0000

Sorry, have been busy with other things. I looked at it a bit but couldn’t find anything. I might have some time to take another look at it this weekend. I wasn’t able to reproduce the bug in Chrome, so it’s possible that it is a Firefox issue.

By: PaulCormier

PaulCormier — Thu, 28 Apr 2011 15:29:00 +0000

Any progress on this bug?

By: Uwe Jakobs

Uwe Jakobs — Sat, 23 Apr 2011 13:08:00 +0000

Hi Stephen,

thank you very much for this plugin. I’m using it for displaying Flash-Banners on a Typo3-Site. It’s working great!

Nevertheless, I had some problems to create a proper count on Flash-Banner-Clicks. This is a general problem with the Flash-Technology, so the only chance you have is using an EVENT inside the surrounding Tag. Because each banner has to have an unique count, you will want to work with parameters to guarantee a valid identification.

Therefore, I added an onmousedown-Event for the Object-Tag in your plugin-code. Now, it’s quite easy to call another javascript-function, that does the job (in my case, it’s an AJAX-driven MySQL-Insert).

You may download the zipped files here, if you like:
http://imageco.de/jquery.flash.zip

HTML-Snippet to give you an idea what I’m talking about:

######## jquery.flash ########

$(document).ready(
function () {
$(‘#add_’.$row["UID_PL"].”).flash(
{
‘src’:”.$img_pfad.$row["file"].”,
‘id’: ‘flash_’.$row["UID_PL"].”,
‘onmousedown’: ‘javascript: bannerCount(‘.$row["UID_PL"].’)',
‘width’: ’160′,
‘height’: ’600′,
‘wmode’: ‘transparent’
}
);
}
);

You need to install flash.’;

######## jquery.flash end ########

I hope, my solution can help other people too.
Please excuse my bad english, I’m still learning

Cheers

Uwe

By: PaulCormier

PaulCormier — Tue, 22 Mar 2011 01:15:00 +0000

Great thanks. Let me know if you need help trying/testing anything. The odd part is the first call has the “If-Modified-Since” header where the subsequent ones do not?!?

By: Stephen Belanger

Stephen Belanger — Mon, 21 Mar 2011 20:29:00 +0000

Hmm. Good question. I’m not sure why it would be doing that, as the code doesn’t touch that stuff at all. It’s possibly because the code uses string concatenation rather than object construction and lets jquery deal with that. Perhaps it is generating an entirely new object for each and the browser thinks they are different for some reason. I’ll look into it, if I figure anything out I’ll make some changes and release a new version.

By: PaulCormier

PaulCormier — Mon, 21 Mar 2011 14:56:00 +0000

I’m successfully using your plugin to load multiple copies of the same swf (different IDs) on the same page. The problem I’m having is that the first swf instance loaded correctly checks the browser cache, but all subsequent instances of the swf on the same page DON’T check the cache and instead download from the server.

Firebug reveals that the first instance has “If-Modified-Since” and “If-None-Match” request headers, but the subsequent requests to the exact same swf do not have those headers. All the other request headers (keep-alive, url, etc) are identical.

I’m using v 1.3.2. Any ideas on how to fix this? The SWF is quite large, so it’s important that it pulls from the browser cache after the first load.