Milonic JavaScript Menu

It's just overriding the definitions of the onclass and offclass CSS styles. Sorry I wasn't clear on that.

Actually, I found the tiny little bits of code that are causing the problem: the change from
>> if(_MS[65]){
_brdsty="solid";
if(_MS[64])_brdsty=_MS[64];
_brdcol=_MS.offcolor;
if(_MS[63])_brdcol=_MS[63];
>> if(_MS[65])_brdwid=_MS[65];
_brdP=_brdwid+"px "+_brdsty+$$;
_brd="border:"+_brdP ...

FYI, I've tracked down the behavior change to between the two pre-release versions built Friday January 28 2005 - 17:26 and Tuesday February 1 2005 - 7:26. If there were more in between, I was unaware of them, so I can't narrow it down any further.

Thanks for any help!

I just upgraded to the latest (yes, *latest*) version, and suddenly menu and menu item borders, as defined in CSS classes and applied to divs, are being clobbered or ignored entirely in IE 6.0.29. Has anybody else noticed this? In Firefox it works the same as it always has. I would just put the ...

The newest version took care of most of the button behavior -- thanks for getting it out so quickly, guys. :) Though there is one more little irksome thing:

If I use an onclass = clickclass, the button depresses on mouseover instead of just on click, but if I use an onclass = offclass, the clicked ...

Hooray! Problem solved! Thanks, guys.

That only solves a small part of the problem. The unbuttonlike behavior I'm trying to avoid is the button "depressing" on mouseover. I want it to only depress when clicked, like a real button.

I took a look at the TreeMenu and CollapsibleMenu, and neither of those is what I'm looking for -- I really do want menus with fly-outs. The ideal behavior that I'd like to achieve is to have a fly-out open on mouseover, then have a click to the parent item make it stay open no matter where the ...

No, I can't provide a test page, but I did create a small sample that behaves exactly the same. Due to the somewhat sensitive nature of the menu data (private client information), you'll notice that the sample actually contains a massively pared-down and modified version of the Milonic site menu ...

I've just upgraded to the latest version (5.69, as of this morning), and I'm noticing some odd behavior with combinations of openonclick, closeonclick, keepalive, and retainclickvalue.

Using the globals and styles as defined below, I find that:
1) A click to the topMenu properly opens and keeps ...

It looks to me a lot like all the "click[X]" properties are completely unimplemented. This is more than a little frustrating.

And guys, while you're working on that, could you please make those properties analogous to the on/off properties? That is, for each of the on/off's, have a click version ...