The Nightmare that is “_blank”: Part II (resolved???)

UPDATE: I have found the issue with IE & pop-up blocking. It was not in fact the fault of SWFObject. Rather, the issue was a particular parameter entry: wmode=”transparent”

Yes, the simple removal of this entry caused IE’s pop-up blocking to cease. It appears I finally have a working solution - I tested on: XP (IE6, Firefox, Safari 3, Opera) & OSX (Firefox, Safari 3, Safari 2). The only caveat now being that the use of wmode=”transparent” causes IE to pop-up block.
Okay, I am putting this out to all of my readers…


I’ve almost got every browser working for my “_blank” clicks. The final exception is that on IE clicking is triggering a pop-up blocker. Surprisingly, it is not my code that appears to be the issue - or at least not directly - rather, it appears to be caused by the use of SWFObject to embed the .swf file. (We use SWFObject for our .swf embedding for a variety of reasons.)

Below are three links to my “Example 2″ , each using a different loading method. Standard as generated by Flex, SWFObject 1.5, & SWFObject 2

http://www.easternstorm.net/sassie/example2/example2.html

http://www.easternstorm.net/sassie/example2/example2-swfobject.html

http://www.easternstorm.net/sassie/example2/example2-swfobject2.html

If anyone can provide insight as to why the use of SWFObject is triggering the IE pop-up blocker, please, please let me know!

- The Saj

PS - Here are a few additional links on “_blank” issues. These demonstrate examples of using Callback, which I have not implemented but might consider incorporating.

Insideria

AssertTrue

10 Responses to “The Nightmare that is “_blank”: Part II (resolved???)”


  1. 1 Jim February 12, 2008 at 10:10 pm

    I notice that it’s now a Nightmare with a capital “N” :-)

  2. 2 thesaj February 13, 2008 at 9:20 am

    Hmm….must be my sub-conscience expressing it’s frustratioN. ;-)

  3. 3 Bartek Drozdz April 1, 2008 at 3:00 am

    Finally a solution that works (swfobject 1.5 and 2) in Firefox. Thanks! I also checked and it works on IE 6 and Safari 3.1 on Win. I didn’t test it on IE 7… It is sad such a basic functionallity is causing such big problems.

  4. 4 Jaz April 8, 2008 at 6:22 am

    I came across this topic while searching for an answer on exactly the same problem. I’m using SWFObject but it seems to work on all browsers aside from IE7. Any insight would be much appreciated.

  5. 5 thesaj April 8, 2008 at 9:47 am

    If I recall correctly, the wmode had an effect on IE. You can try changing it to “opaque” or “transparent” and seeing if that works.

    That said, when you say “all browsers” did you test both Safari 2 & Safari 3. They behave much differently.

    - Jason

  6. 6 Willow Wright June 3, 2008 at 1:11 pm

    Well, all of this is fine…..I really need to use wmode = “transparent” and that brings up the pop-ups blocked. And I’m not even asking the browser to open a new window…..not even asking for a target. No javascript to open anything new. And STILL I get the pop-ups blocked.

    I am about to junk AS3, and go back to AS2, in which I have NO problems of this sort.

    So far, I’ve not been able to use one AS3 script in Flash on my site, and I’ve had the new CS3 software for a WHILE.

    Does anyone have a solution for my issue? Thanks, WCW

  7. 7 Jonah June 3, 2008 at 6:52 pm

    Hello
    My name is Jonah Huggins, and I am a programmer trying to figure out a simple syntax problem that I am having with an AIR app that I am writing.

    So here is what I am trying to do…

    I am trying to send the text that is stored in a variable to my SQLite db. I have no idea what the syntax is but I know that it is simple…

    Here is a bit of my code where the problem occurs.

    private function postComment():void {

    var commentVAR:String = commentText.text;
    //Alert.show(commentVAR);

    var q:SQLStatement = new SQLStatement();
    q.text = “UPDATE data SET comment=commentVAR WHERE prim = 1″;
    q.sqlConnection = conn;
    q.addEventListener( SQLErrorEvent.ERROR, queryError );
    q.execute();

    //Alert.show(q.text);
    }

    As you can see I am trying to update a field by sending it the value of the variable “commentVAR”… We have tried countless syntaxes and researched for hours with no luck or example of what the syntax is for doing this simple thing, we have even tried just updating with commentText.text but “commentText.text” is what gets stored…

    Ps. Everything else works great, but when we try to get the variable’s data stored in the db it just stores “commentVAR” instead.

    If anyone could help me out on this it sure would be appreciated.

    Thank you so much :

    Jonah Huggins

  1. 1 Problems using navigateToURL - aron / philipp development blog Trackback on April 8, 2008 at 4:59 am
  2. 2 UPDATE on “_blank” / navigateToURL() issue « The Saj - S.A.S.S.I.E. Trackback on May 30, 2008 at 4:04 pm
  3. 3 FlexMerge » Opening External Links from AS3 Trackback on June 30, 2008 at 12:15 pm