Ignore target="_blank" ... External links using this in the CMS now seem to ignore it?

Options

I'm doing a very simple HTML 101 command in which some of my external links, when required by others i work with, are given the inline target="_blank" so that our foundation's website doesn't disappear but rather steps aside as a new tab/window is opened to temporarily show an external link's content.  Also not working is target="_Parent" , target="name", "_self", and style="target-new: tab;"

 

While this basic code worked earlier this year (at least into Spring), i noticed over the past few months it had stopped working uniformly across all instances (we had embedded in several a display lists for opening PDFs and Videos). 



If i export this same CMS page into an Eclipse/notepad environment and launch the html file through any browser, the inline target works as it should (and as it always had since 1995,)  So is there something Convio added to prevent our sites from even a simple manipulation of a user's browser window?  If so, why? Security? 

 

Anyone interested in a quick test can see our site: http://www.americares.org/ and my attempt under the You Can Help tab and any of the two graphical event banners in there. 

Comments

  • I looked at the source with Firebug and only found target tags for the expand links in the tweet tab of AmeriCares Real Time. Which banners are you refering to again?

  • Brian Mucha:

    I looked at the source with Firebug and only found target tags for the expand links in the tweet tab of AmeriCares Real Time. Which banners are you refering to again?

    In the Masthead at the top of the page there's a navigational block floating right of the logo. The dropdown is under 'You Can Help'



    Thanks for looking
  • M OConn:
    In the Masthead at the top of the page there's a navigational block floating right of the logo. The dropdown is under 'You Can Help'



    Thanks for looking

    Ahh, gotcha. The image links IN the drop-down.

     

    I've never seen the style trick, but the target tag looks correct to me.

     

    I don't see how Luminate could stop that from working even if they wanted to (aside from not rendering the target tag at all). Its all client side behavior.

     

    What the heck?!

  • Brian Mucha:

    Ahh, gotcha. The image links IN the drop-down.

     

    I've never seen the style trick, but the target tag looks correct to me.

     

    I don't see how Luminate could stop that from working even if they wanted to (aside from not rendering the target tag at all). Its all client side behavior.

     

    What the heck?!

    Okay, I took a look at scripts in Firebug, and it refused to show the local scripts - it kept telling me to reload. If I disable JS using the Web Developer extension, the target tag works fine.

     

    Something is up with a JS that is causing this.

  • Brian Mucha:

    Okay, I took a look at scripts in Firebug, and it refused to show the local scripts - it kept telling me to reload. If I disable JS using the Web Developer extension, the target tag works fine.

     

    Something is up with a JS that is causing this.

    Firebug also does not like the comments like this:

     

    <!----------------------------------------------------->

     

    "Consecutive hyphens did not terminate the comment."

     

    Firebug also reported several stray </div> and other tags. Perhaps related to the above.

  • Brian Mucha:

    Okay, I took a look at scripts in Firebug, and it refused to show the local scripts - it kept telling me to reload. If I disable JS using the Web Developer extension, the target tag works fine.

     

    Something is up with a JS that is causing this.

    Could it be something with Google Analytics inline link tracker, which I think is on both sites, that has also been overhauled on Google's end since Spring?
  • Brian Mucha:

    Firebug also does not like the comments like this:

     

    <!----------------------------------------------------->

     

    "Consecutive hyphens did not terminate the comment."

     

    Firebug also reported several stray </div> and other tags. Perhaps related to the above.

    Just as a test to a page that hasn't been upgraded in *quite* awhile (was built in 2008), I did a quick test on http://www.americaresfreeclinics.org/, in case it has something to do with headers or current cocktail of jQuery behaviors on our main site (which was recently updated)



    What I did here was I also added the "target _blank" inside the Masthead navigation dropdown under Donors > Donate Now. Same behavior. Hmm.
  • M OConn:
    Just as a test to a page that hasn't been upgraded in *quite* awhile (was built in 2008), I did a quick test on http://www.americaresfreeclinics.org/, in case it has something to do with headers or current cocktail of jQuery behaviors on our main site (which was recently updated)



    What I did here was I also added the "target _blank" inside the Masthead navigation dropdown under Donors > Donate Now. Same behavior. Hmm.

    I was going to say no to the link tracker idea, but a quick GIS says yes.

     

    http://stackoverflow.com/questions/4278529/use-google-analytics-asynchronous-version-to-track-outgoing-clicks-without-bre

     

    http://stackoverflow.com/questions/9379615/onclick-for-google-analytics-and-target-blank-the-link-does-not-work

     

    How about that?

  • Brian Mucha:

    I was going to say no to the link tracker idea, but a quick GIS says yes.

     

    http://stackoverflow.com/questions/4278529/use-google-analytics-asynchronous-version-to-track-outgoing-clicks-without-bre

     

    http://stackoverflow.com/questions/9379615/onclick-for-google-analytics-and-target-blank-the-link-does-not-work

     

    How about that?

    Funny, huh?

    So I take it that this would be a web-wide issue because many companies still use target as a interface strategy? And I was thinking of - but avoiding until last resort-- using vanilla javascript to open new windows/tabs, looks like I will now.



    Thanks for taking a look at this, Brian! And now you have the answer in your forums in case someone asks...
  • M OConn:
    Funny, huh?

    So I take it that this would be a web-wide issue because many companies still use target as a interface strategy? And I was thinking of - but avoiding until last resort-- using vanilla javascript to open new windows/tabs, looks like I will now.



    Thanks for taking a look at this, Brian! And now you have the answer in your forums in case someone asks...

    If this really is the issue, I wonder if going back to the old Analytics JS would fix it? The first link specifies the async version.

     

    I'm pretty astonished that something as universal as Google Analytics could break something as univeral as target tags!

     

    Welcome. Sometimes a new set of eyes for a few minutes is all that is needed.

     

    / Now we have the answer in our forums.  :-)

Categories