Milonic JavaScript Menu

Just an additional FYI... I just installed NS 8.01 and tested it and the problem does NOT exist in the latest NS version. Not sure what the issue may actually be with 7.2... but I'll create the test anyway and get back with you guys.

Regards,

Brett

John...

Thanks for the suggestion. Great idea. I'll create a test scenario myself and see if the issue still exists in the current DHTML menu. If so, I'll report it and provide a link to a sample that can demonstrate the condition.

Regards,

Brett

Hi Ruth...

Thanks for the suggestion. I posted a message in the Anything Goes section, at one point. The subject was Enhancement suggestion... or something like that. Anyway... I described the functional change that occurred in the long menus support... basically... they changed the way the long ...

Hi...

I have a client with an application I wrote that uses the DHTML menu, Version 5.0 Release Candidate 4.0 (I know that's an older release candidate, but I can't upgrade it, because functionality I need was changed.)

Anyway... this issue has just popped up for me with a client that is accessing ...

Hi...

I have a program that dynamically writes the menudata.js file on the server. On one of my web pages I have maintnance facility that allows the user to specify what appears on one of the submenus. After they submit their changes, I call my program and regenerate the menudata.js file, then I ...

Hi Andy...

If you view http://www.zware.net/screens.htm it should help clarify the concern I have for vertical submenu alignment.

Thanks,

Brett

I may have posted something about this a while back, but I'll submit it here again...

I'll start by saying the overflow scroll functionality is a wonderful enhancement to the Milonic menu. In earlier versions the top of the vertical submenus aligned with the parent menu item they were related too ...

Why is there such resistance to providing support for frames??? I've read all the comments on frames and I can't help but respond that frames is still a very real functional component of site design. Some designers even build frames within frames to acheive the type of functionality that meets their ...

Hi...

The sample you provided works great... I thought I'd add a litte tweak that I applied based on the disclaimer you made. (line hilited in bold blue, below)...

I added a function just like your distantMenu() function, except all it does is hide menus in the target frame. That way when I hover ...

Hi Dave,

I could not find the long menus sample on the Milonic website. It's almost as if that great feature has been played down. In any case, I went ahead and built a menu that would trigger the long menus flag (scrolling) and after it adjusted to use as much screen space as possible, it turned ...

Hi Dave,

Thanks for the feedback. I completely agree with you. Sometimes I forget that the menu is still in beta mode. I had to use it in a website I designed because I needed the support for long menus. It was not optional.

In any case, I appreciate the feedback that I got today. I'll definitely ...

Okay... after a little more testing I've found that if I set the variable _subOffsetTop to a value of 0, Netscape 7 handles the positioning of my submenu (box) perfectly, regardless of whether or not I maximize the browser window or not.

On IE setting the value of _subOffsetTop to 0 causes my ...

Here's what I just discovered. This offset positioning seems to be affected by whether or not your browser is maximized or not. If I have mine maximized, the -3 value works fine. If it's not maximized, I have to change it to +4. Very strange.

Seems there is an issue with how menu positioning is ...

I removed the _c and the scriptpath variables across the board and left Andy's if(ns4) test in place. Now the Javascript runtime error is on line 15 instead of 17. (Accounts for the 2 lines I removed from the milonic_src.js file for scriptpath and a blank line.)

Now for some reason or other, my ...

John... Thanks for the input. I just copied the if(ns4) test from Andy's menu.htm file, pasted in place of the version I had and the very next time I brought my page up, I got the Javascript Runtime error on line 17. The menus no longer display. I'm using IE6 Version: 6.0.2800.1106.xpsp1.020828 ...

By the way...

After all these changes... when the scrollbar does display in IE6 the horizontal scrollbar still appears at the bottom of the submenu, so the upgrade did not resolve the issue.

This problem does not occur on NS7.

Brett

I just experienced a very minor alignment issue after implementing the V5RC17 menu. I had to adjust the _subOffsetTop variable to -3 to overcome the issue. You might experiment with those variables and see what you come up with.

Also I had some issues with the way that particular script block was ...

Okay, I've bitten the bullet and upraded to V5RC17.

I resolved the issue of the text box not displaying properly by setting the value for the variable _subOffsetTop to -3.

Everything lines up fine in both IE6 and NS7.

I'm still bothered by the fact that the menu adjusts my submenu position upward ...

Okay... I traced down the issue regarding not being able to run the current version of the menu. In the V5RC6 release, there was not a requirement for me to load mmenudom.js or mmenuns4.js. (Or at least not explicitly). My menus worked fine.

On the current version, I hard coded the statement to ...

Hi Kevin...

Thanks for the quick response. I downloaded V5RC17 and followed my usual process for updating the objects in my website (development), which is to review the readme's then I overlaid the previous milonic_src.js, mmenudom.js, and mmenuns4.js objects. I edited the milonic_src.js file and ...