Milonic JavaScript Menu

Thank you, problem has been fixed - in IE7 was a bug in a map application.

Here is page http://t-mobile.cz/Web/MapMilonicTest.html with disableMouseMove=true;

Map application now works fine - but when the move button is clicked, the menu stops work.

I have to apologize - the problem is not with onmousedown handler but with document.onmousemove .

This is set inside $N function called by a timer and this timer is set inside function o$.

The first (affected) page has incorrect handler:

function gMY(e){if(ns6){X_=e.pageX;Y_=e.pageY}else{e=event ...

I can confirm that document.onmousedown is executed only once when the menu is loaded.

This means you can override it.

I analysed actions of menu code and found that problem is caused by incorrect setting of document.onmousedown handler.
It is set by only once but by a timer, so It happens after ...

Thank you for your reply. I will try to deactivate URL matching - but I cannt find page with global properties it seems to be missing http://milonic.com/global_properties

Is it possible to disable URL matching?

I am shure that document.onmousedown is set by the menu function called by timer - thats why it doesnt depend on script order.

I think menu code should assume that somebody other have set document.onmousedown first

Here is example with "very first menu code" - it doesn't work:
http://t-mobile.cz/Web/MapMilonicTest.html

Here is the same page, but drawMenus() is commented - every scripts are loaded, only drawMenus() function is skipped - and map application works:
http://t-mobile.cz/Web/MapMilonicTest2.html ...

Thank you for the answer, I have tried declaring the menu as the very first JavaScript object on the page but it has no impact, problem persists

Does the menu use really correct way to attach event handlers?

I have conflict with menu and AJAX application.
Menu hardly replaces document.OnMouseMove and application doesn't work correctly - you can see example on http://t-mobile.cz/Web/Residential/TarifySluzby/MapaPokrytiCR.aspx - if you switch map application from rezise to move mode (by clicking http://t ...

Thanks for your reply, but this problem is not about using tooltips - I completly dont use tooltips, but the problem with "tooltips in error message" still persist, it probably depends on some changes in menu due tooltips upgrade?

JavaScript error appears if you move on item, which call popup menu, but definition for this item is missing in data file.

Line: 21
Char: 8397
Error: '_m[...].tooltip' is null or not an object
Code: 0

Try move mouse over link "t-zones"
http://t-mobile.cz/Web/Default.aspx

Is possible to correct ...

Thanks, it works fine now, but in Opera is some position bug - submenus are rendered about 15px lower than in IE, FF:

http://t-mobile.cz/Web/Default.aspx

Problem persist in 5_733 final:

If you expand some level of menu (mouseover) and first item has a submenu, it will not be expanded on first time you move over - item will be expanded after you move over other items of menu and return to the first item.

> please check the Milonic main site and see if the problem occurs on that browser for you

There is a problem - the Milonic main site menu doesnt contain any item, which has submenu on some first item, because the bug is not possible to demonstrate.

HTML code, data file and stylesheets:

http://t ...

I have to use 5_731 version, because latest version in IE6 (in Opera works fine) the first child of menu is not expanded on a first try - user have to move to second or next subitem and then can be first child expanded on mouseover.
Will be this problem solved in final 5_733 ? Thanks

Its exactly this problem, thanks for your cooperation

Problem appears only if I set

fixMozillaZIndex=true;

Items with subitems stay in "onmouseover" state, and subitems not expanded.

In this time I cant get url to check - maybe somebody have the same problem, or I will wait to the next version, i will see...

Previous version still work correctly, but in version 5.724, 5.725 the subitems are not expanded in FireFox 1.0.4
Does anybode have the same problem? Will be fixed this problem in next versions?