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:54

Too many warnings!!


Poster: perldev
Dated: Thursday February 3 2005 - 22:11:16 GMT

When I open http://www.milonic.com with FF. There are too many javascript warnings, most are like:

Quote:
reference to undefined property _mi[_x][3]
Source File: http://www.milonic.com/mmenudom.js Line: 16


The undefined properties are: _I[xx], _gmi.pt, _bwC, $G.border, .. too many to list.

Shall we worry about the warnings?

..


Poster: fletchsod
Dated: Thursday February 3 2005 - 22:22:44 GMT

The javascript warning in Firefox and Mozilla are a feature that was added about a year or 2 ago. The reason you see too many warning is because it is what it is shown when the Milonic's javascript is continously running.

I have that same problem because it make it harder for me to debug the website with the javascript console. I had to comment out the Milonic script to debug it or something.

FletchSOD


Poster: John
Dated: Thursday February 3 2005 - 22:31:50 GMT

Exactly where are you seeing these warnings? I just went in with FF and got no errors at all.

..


Poster: fletchsod
Dated: Thursday February 3 2005 - 22:51:10 GMT

With the JavaScript Console...

Tools --> Web Development --> JavaScript Console

Well, I can't read enough to copy it and give an example here because it is generating too many warning message at once. It's like trying to read 500 pages textbook in 5 seconds.

FletchSOD


Poster: perldev
Dated: Friday February 4 2005 - 1:39:02 GMT

Web Developer >> Options >> Javascript

turn on " Enabel strict Javascript warning"

Then you will be able to see all the warnings when visiting milonic site and opening the java console.


Poster: John
Dated: Saturday February 5 2005 - 2:54:43 GMT

Well, I just got a pile of errors when going to another user site that was not working properly, so I have to ass-ume the console is working properly. However, going directly from there to Milonic home with the console still open I see no errors whatsoever.


Poster: mtd_conseil
Dated: Wednesday August 17 2005 - 13:16:55 BST

Hi,

I just felt on this error, massive pile of warnings in FireFox :roll:. Here are a couple I copied for you.

Quote:
Warning: reference to undefined property $G.border
Source File: http://www.milonic.com/mmenudom.js
Line: 16

Warning: assignment to undeclared variable _gs
Source File: http://www.milonic.com/mmenudom.js
Line: 16

Warning: assignment to undeclared variable _Cr
Source File: http://www.milonic.com/mmenudom.js
Line: 16

Warning: reference to undefined property $y.kAm
Source File: http://www.milonic.com/mmenudom.js
Line: 16

Warning: reference to undefined property _I[34]
Source File: http://www.milonic.com/mmenudom.js
Line: 16

Warning: assignment to undeclared variable b_help
Source File: http://www.milonic.com/forum/posting.ph ... 17fd8e06c0
Line: 271


You must have the "web developper" extension to see them and must activate the "Enable strict javascript warning" option.

Those "warnings" are not "errors". It does seem to affect the menu running but it should be something to work on because it could become a problem. Normaly, that's what warning mean, doesn't it? Moreover, when you try to correct other javascript in the page that has nothing to do with the menu, it's a pain because it goes more than hundred of warning.

I have this pile of warnings on any website, even Milonic.com, that has the menu on them and I don't get them anywhere else except for other kind of errors.

Does something has been done about it yet? just asking. ;)

Best regards,
Mike


Poster: John
Dated: Wednesday August 17 2005 - 14:48:25 BST

Assuming your site is still http://www.virtuelcom.com/, I just went there using the settings you described and got no errors at all. I did, however, get a pretty good pile on the Milonic site, so I know the extension is functioning properly.


Poster: mtd_conseil
Dated: Wednesday August 17 2005 - 15:19:48 BST

hi,

that's normal, it beautyfull isn't it? ;) I'm kidding.

I'm a resseller, I build websites and sell them. This version of the website has no milonic menu in it yet because we are rewriting the new version actually with one menu.

Just go on http://www.milonic.com or any websites that has Milonic menu in them in the list on milonic client's website. Actually, we have over 10 websites on our behalf with Milonic menu and they all do this behavior. But we find out only this week beause of anotehr problem on a web sites forced us to active the option and then we saw all those. At first, we thought we were having problems and then we found this thread and tried it on many other websites that has nothing to do with us.

Don't mistake me, they are not errors, they are warnings, and to see them, you must activate the right properties. But it does not seem to affect the good working of the menu.

Like I said in the previous mail and like others said (since I'm in the right thread), those are not default setting or Firefox. If you take FireFox as is and try it, you will never see them. It's for advanced developpers with the right extension plug-ins.

Also, when you move mouse over stuff and opening and closing menu, the list gets longer, so the warnings continues. It's not just at first load problem or a before initialization problem. At the same time, maybe it's nothing at all and that's the way Javascript go. I'm not going to investigate this problem since I'm not on the development team and we already have a big overhead on our on work.


Where is a screen shoot of error took directly from milonic website.


Image


I hope by teaming together, we will be able to find where those lurky warning are coming from! ;-)

Cheers,
Mike


Poster: Andy
Dated: Thursday August 18 2005 - 7:14:00 BST

They are just warnings and nothing to worry about.

Most of them appear to be related to variables and objects that have not been pre-defined.

We don't pre-define variables in the menu in order to keep file sizes down. If we did, it would probably double the file sizes.

They are completely benign and can be ignored.

Cheers,
Andy


Poster: mtd_conseil
Dated: Thursday August 18 2005 - 13:13:14 BST

Good,

that reassures me.

Cheers,
;-)