Milonic provide full featured pull down web menus for some of the worlds largest companies
click here to see what it can do for you

Download Milonic DHTML Menu
Buy Milonic DHTML Menu

Back To Start Of Archive
Taken From The Forum: Help & Support for DHTML Menu Version 5+
Forum Topic: Click to view post
Last Updated: Saturday July 14 2012 - 06:07:31

Ns4.x crashes with all 5.0 menus


Poster: janellepeterson
Dated: Thursday April 29 2004 - 1:52:16 BST

Have a non-profit freeware early version of the menu posted at http://66.175.47.101/ . Spent most of the last couple of days making sure the dang thing would work in the dreaded IE 5.2 for mac - and came to the conclusion that I needed to purchase a professional version of 5.0 in order to get the most out of cross-platform compatibly.

However... testing the 3.0 menu in Ns4.05, it works okay - the color is off and there is that pesky problem where the menu ducks behind the text input box for the search. But... try out any of the 5.0 menus in NS4.05, it crashes. Crashes on the milonic site when you go to mouseover, gives random javascript errors - and while testing out browsercam.com gave really nasty errors for netscape. I wouldn't really care, but the .org's networks are all set up to use Netscape 4.7 - so it needs to work. Planning on purchasing, but need to clear that up first.

http://66.175.47.101/version5/menu.htm (this is the preview of the v 5.0 menu - can anyone tell me what may be wrong?


Poster: Ruth
Dated: Thursday April 29 2004 - 7:35:58 BST

I am not seeing a problem with your menu [of course, I could be missing something, it's late :) ] The menu works fine in netscape 4.79 which is the oldest netscape I have [release 9/99] 4.05 was a 6/1998 release, the newest being 7 series, which uses a totally different code base [starting with 6] than the 4x series. Not having that browser I can't test to see why it's doing what it's doing. But, I did want to let you know it works fine in 4.79. You might check to see just how many users actually use that browser when visiting your site. You might check this topic. The person here codes the page to ignore the menu if it's a netscape 4x browser and instead places a text alternative there. http://www.milonic.com/forum/viewtopic.php?t=3692 and this is the link to see how it works on the site, you might check it in a newer browser to see the actual menu, then the older one to see how the alternative was placed. It seems to be a pretty good working alternative for the very old browsers. http://www.citytech.cuny.edu/ I'm sorry I can't be more help. Perhaps someone else will be able to give you better information on this issue.

Ruth


Poster: kevin3442
Dated: Friday April 30 2004 - 22:34:51 BST

At a quick glance, I see some problems in your menu_data.js file. Syntax is not always correct, and you've incldued several "preoperties" that do not exist in the menu. For example, in
Code:
aI("text=Explore Kodiak <img src=http://66.175.47.101/menu2/blank.gif border=0>;image=http://66.175.47.101/menu2/xpblank2.gif;showmenu=Explore;url=http://66.175.47.101/explore.htm;status= # offbackcolor=669999; onbordercolor=99CC99;offbordercolor=831F48;")

When mousing over this item, the browser's status bar will actually contain "# offbackcolor=669999" because the status text ends at the semicolon. If you intended offbackcolor=669999 to set a color property, it won't work even if you get the status semicolon in there, because offbackcolor isn't a menu property. offbgcolor is a property (maybe the one you want), but the syntax to set it would be offgbcolor=#669999 not offbgcolor=669999. Similarly, onbordercolor and offbordercolor are not menu properties (they don't exist in this context). As finicky as NS4 is, your code should be very tight if you want to put it in NS4.

You might want to look at the quickrefs on style properties, menu properties, and menu item properties to see what properties are avilable, then look at a variety of samples to see how the various properties are used.

Hope that helps,

Kevin


Poster: Ruth
Dated: Saturday May 1 2004 - 3:49:17 BST

:oops: geesh, I must have had my eyes closed when I looked at that!