mmenudom.js error in Netscape 6.2

Poster: jbreslow
Dated: Friday January 23 2004 - 0:02:32 GMT

I am getting an error in Netscape 6.2 (and that seems to be all) that says...


Warning: test for equality (==) mistyped as assignment (=)?
Source File: mmenudom.js
Line: 16, Column: 233
Source Code:
m!=_n){_t+=_tgm.offsetTop;_tgm=_tgm.offsetParent}...
[snipped by Admin for ease in reading other messages]

any idea how to fix this? I have downloaded the latest version and I get the same error.

Poster: Ruth
Dated: Friday January 23 2004 - 0:12:55 GMT

A link would help a lot so they can see the problem in action. I just tested the latest release 44 in Netscape 6 and get no error message like that.

Poster: John
Dated: Friday January 23 2004 - 2:42:53 GMT

We really need specifics ('latest version' doesn't tell us anything, as often there will be more than one release a day). OS and version, RC AND build date, etc. And, as Ruth said, a URL (as is requested on the posting page).

Poster: jbreslow
Dated: Friday January 23 2004 - 15:48:39 GMT

Hey,

I hope I'm giving your the right information, I have no idea what RC and build date are, but my Sysadmin says it's...

SERVER
RedHat 8
Kernal 2.4.20-28.8 SMP
I686 Platform


I'm viewing it in Win 2000 SP4. And I'm sorry I can't give out the url, it's password protected, the site not the url.

Any suggestions???

Poster: jbreslow
Dated: Friday January 23 2004 - 17:57:24 GMT

Found a site that is open to the public where you can view it.


http://av-rooms.ucsd.edu/av_services.cfm



TIA

Poster: John
Dated: Friday January 23 2004 - 18:24:22 GMT

Not exactly what I was after (thanks anyway), but the URL really helped.

Here's the major problem...

You folks are running Version 5.0 Release Candidate 6.0 Built: Wed August 20 2003 - 17:12 (contrary to your comment about running the latest version!).

The current release is Version 5.0 Release Candidate 44 Built: Friday January 23 2004 - 11:19! This info is located towards the top of the comments in the menu code files.

Given that there are usually multiple releases under the same RC (the 'Built' date changes), you are not simply 38 versions down-level, but probably well over 50!

So...

1. Download the current version from http://milonic.com/.

2. READ the included files, as the install is now quite different from the version you are currently running.

3. Compare the syntax of your _data file against the sample included in the download. There have been some changes there as well.

4. Subscribe to http://www.milonic.com/forum/viewtopic.php?t=3108 by going to that link, and then clicking on "Watch this topic for replies" in the upper or lower right corner of the page. That will send you an e-mail every time I post an announcement of a new release there.

Let us know how it goes.

Poster: jbreslow
Dated: Friday January 23 2004 - 19:25:59 GMT

Now that I know what information you are looking for, here it is... from the page that is password protected...

Version 5.0 Release Candidate 44 Built: Thursday January 22 2004 - 20:29


The url I sent has an older version, but the same error.

I'm not gunna download another version of this menu. It seems that the menus are not backwards compatible and so I'd have to re-format my menu and re-code all of the links. It takes too much time to get it to look exactly the way it needs to. I've done this before and it was not fun.

Don't get me wrong, Milonic has a great product and some great support. I just don't have the time to redo my menus every time a new version comes out.

Poster: John
Dated: Friday January 23 2004 - 21:20:57 GMT


Nowhere did I say the data has to be rewritten every time a new menu comes out. In all the v5 releases it has happened maybe 2 or 3 times, and that was early on in the development. My comment was based on the RC6 page you sent me to.

There's really not much we can do to help if we can't actually see the problem. In many cases we've been able to when we have seen a problem before, but I have not seen this error reported until now.

Poster: jbreslow
Dated: Friday January 23 2004 - 22:05:55 GMT

No, you did not say that it would need to be rewritten. Since things do not appear to be backwards compatible, I can't use the new file mmenudom.js with the old milonic_src.js, mmenus4.js, etc... so I would need to recode all of my links. Is that not correct? Can I use my current file with all the setting in it, menu_data.js with the new versions of milonic_src.js and mmenus4.js.

So, what now?

Thank you again for the help.

Poster: John
Dated: Friday January 23 2004 - 22:26:52 GMT

The question now is which site are you talking about? I'll 'assume' it's the one currently running RC44. If that's the case, and you have made previous syntax updates to your data since the RC6 posting, and you have made the changes to the JS calls quite a few releases back, and you are no longer using scriptpath=""; in your code, then there should be no changes to make to your data. Again, I say 'should' because we can't see how you have things coded, so this is all guesswork.

Re: mmenudom.js error in Netscape 6.2

Poster: kevin3442
Dated: Tuesday January 27 2004 - 0:50:47 GMT



Let me add my two cents...

The above message is not an error, it is a "warning" -- there's an important difference between the two. An error will definitely affect processing somehow; a warning is something that the js interpreter built into the browser suspects may be a potential error (a "maybe"... hence the question mark after the warning message). A warning does not necessarily affect processing. In this case, the interpreter is looking for a common syntax error (typing an assignment operator '=' instead of an equality operator '==').

The code snippet you posted does not occur in RC6's mmenudom.js (but it does contain an earlier version of similar code). It does, however, occur in more recent RCs, including the current one (RC46). Anyway, from the snippet, I don't see anything that would warrant such a warning; the code snippet contains only one pure assignment, and it is definitely a valid assignment, not a mistyped equality check (if it was a buggered equality check, then the menu positioning would be all screwed up). All that shows me is that NS6.2's checker could use some checking! The upshot... it's an unwarranted warning... don't sweat it.

Re: upgrading to the latest RC. You'd have a little work to do to bring the menu_data.js code into line with the current practices (from RC6 to RC46), but not much.. nothing like converting from version 3 to version 5. And comparing the quality and stability of RC46 with RC6, it'd probably be worth it. Once you do the edits, you wouldn't have to mess with it again to keep pace with future RCs and (eventualy) the final production release. BTW: when you update, you can't just update mmenudom.js, you have to upload all three base menu script: milonic_src.js, mmenudom.js, and mmenuns4.js... you probably know that, but just in case someone else is reading this...

Nice looking site BTW.

Hope that helps,

Kevin