Target links don't work in Netscape 4

Taken From The Forum:
Forum Topic:
Last Updated: Saturday July 14 2012 - 06:07:07

Target links don't work in Netscape 4

Poster: EighteenNinetyEight
Dated: Tuesday October 5 2004 - 2:36:09 BST

Hello,

I've designed a page that needs to use target _parent links. The whole page useless without this common ability because I want it to be a tour of my web work with an upper frame that serves as the navigation and tour guide.

http://www.gohrsch.com/portfolio

It works in fine in Netscape 7 and IE 6, but not in Netscape 4.

During testing, i've found that this browser does have the ability to replace all of my page content with new content, however milonic is not sending the target information in its link to netscape 4 as opposed to other browser versions.

I opened up the mmenuns4.js file and there is no code for target. I noticed that target is array number 35 in the milonic_src file. I really need make this work. I trying to figure out how to change the mmenuns4.js file so that it will create links with the target information I've specified.

Can anyone help? Is there another possible work around?

Thanks!

James

Poster: John
Dated: Tuesday October 5 2004 - 3:06:16 BST

James -

First and foremost - NEVER mess with the menu code files! Doing so will void everything (including support).

That said - NS4? Most folks are dropping it like a hot potato, although I do understand (some of) the reasons for trying to keep supporting it.

Next, v5 of the menu system does not (yet) support frames. However, there is an unsupported work-around on the Forum. A Search will find it for you.

Hmmm - sorry to be so negative, but stick with us. We do solve things here! Besides, this is the best DHTML menu system anywhere.

Poster: EighteenNinetyEight
Dated: Tuesday October 5 2004 - 3:38:04 BST

Can you give me the url for this work around please?

Poster: EighteenNinetyEight
Dated: Tuesday October 5 2004 - 4:32:28 BST

Ok, so I solved my little problem by adding a....

Code:

<script type="text/javascript"> if (top.location != location) top.location.href = location.href;</script>

to the head of my framset so any time netscape loads the frameset into a subframe, it will pop out of it.

I still think the mmenuns4.js file ought to also include the target specification.

This was just an easier way to handle it.

J

Poster: kevin3442
Dated: Tuesday October 5 2004 - 6:15:00 BST

Hi James,

I'm assuming you're changing the content frame based on menu selections, right? Instead of relying on a url/target combo, you could call a js function from a menu selection to load a new page into the content frame. In other words, uppose you had a fucntion like this:

Code:

function loadFrame(frameName, URL)
{
  parent[frameName].location = URL;
}

then you could call it from a menu item like this (supposing your content frame is named "main").

Code:

aI("text=Item Text;url=javascript:loadFrame('main','pagename.html')";);

Haven't tried it, but it may be a viable alternative that'll still let you use frames in NS4.

Kevin

Industrial Strength JavaScript and DHTML Menus

Target links don't work in Netscape 4