Hi guys,

Recently, I've been runing into some issues with the firefox popup blocker.

What's happening is that it's kind of overzealous, and is blocking
legitimate, user-initiated clicks.

I've found that the most reliable way of avoiding angering the popup
blocker is by putting external links in HTML textfields - which seems
to work most of the time, but even this method is sometimes failing.

I've noticed that this issue has been discussed before, but no
definitive conclusions appear to have been reached.

I thought it might be a good idea to throw in my observations and see
if anyone else can shed some light on this, as it's a pretty crucial
issue for a lot of RIA developers.

What seems to be happening on my machine is that firefox will block
links from a swf if it recieves too many clicks in a short time, and
once a swf has been blocked, all further links from it are blocked,
regardless of where they go or how they are called.

This is problematic because we are trying to avoid triggering the
popup blocker by only using user-initiated linking methods, and it's
quite likely that the user will click twice, or click really fast if
they're not getting immediate feedback - so they end up triggering the
popup blocker logic themselves. The only potential solution for this
is to somehow route the getUrl calls through some scripted logic which
prevents multiple clicks. However, the fact that the calls are coming
from a script, rather than a HTML textfield,  might in itself make the
popup blocker catch these links.

I think we need to establish how much communication there is between
the flash player and firefox - does anyone know how getUrl calls are
implemented in the mozilla plugin? Whether firefox can tell what
events have triggered the calls? Is there any information given to the
browser as to where these links are coming from, or is the firefox
logic based on just an originator ID and a time limit?

I'd be interested to hear other people's thoughts on this.

Thanks,
Alias

_______________________________________________
osflash mailing list
[email protected]
http://osflash.org/mailman/listinfo/osflash_osflash.org

Reply via email to