[DHTML] Omni Slide Menu script

[jscheuer1]

Hi John:
I've began setting up the page for the menu. Here's the link. The description/ instructions have yet to be put in.

In IE6, one minor issue I noticed is for the right slide out menu. A horizontal scrollbar appears as the menu is sliding out. This doesn't occur in Firefox and Opera that I've tested. Is this an expected behavior/ limitation in IE6 for this menu?

Thanks,

Shaping up! That's a bug that crept in with a bit of advanced IE version detection I (incorrectly) employed, which then allowed me to include some simply incorrect code that never got used. To make a long story short, the mmenu.js file I just uploaded corrects this bug. However, there is something about the demo page that makes the right menu extend a phantom part of itself into the page. This wasn't happening on my demo even before this most recent fix. Perhaps it will go away or be unimportant once you get the current mmenu.js file (I just overwrote the existing one).

One thing I see on the demo page that is wrong (just a hold over from the old FX script, I guess) is that you are still using:

The two files contained are "ssm.js" and "ssmItems.js", both of which you should upload to your webpage directory.

and:

All configurations to the menu are done inside "ssmItems.js". Open the file up using any text editor to edit the menu's style, and the displayed links.

The files are mmenu.js and menuItems.js now.

Also, here is a file to help folks with the configuration. I think it should go in the distribution .zip - I will have more instructions or demos coming:

http://home.comcast.net/~jscheuer1/s...properties.htm

[ddadmin]

Great, yep, the updated .js file fixes the horizontal scrollbar issue in IE6. I've updated the page with it.

, there is something about the demo page that makes the right menu extend a phantom part of itself into the page.

By "phantom", I gather you just mean the menu slides out a little beyond its actual width? It's minute enough that I certainly don't see it as an issue.

One thing I see on the demo page that is wrong ...

Ah ignore that for now. As mentioned the actual description/instruction hasn't been input yet. I'll do that later today, and let you know in this thread when it happens.

Also, here is a file to help folks with the configuration. I think it should go in the distribution .zip - I will have more instructions or demos coming:

http://home.comcast.net/~jscheuer1/s...properties.htm

Great that would come in real handy. Thanks for all the work put into it!

[jscheuer1]

Well, it is still there, only in IE 6 (and probably earlier). I'm not sure what is causing it and it may have nothing to do with the demo page because it comes and goes. If you scroll the page down, and approach the right menu from its left, you don't have to actually hover it to have it extend. It is because the container (motion) division is getting enlarged but, I'm not sure why. If you approach it from the top or bottom, it goes back to its correct size. I could try assigning the motion functions to the next division in or track down what is making the outer one expand. No time right now though. I will get to it later.

[jscheuer1]

I was right, the problem was:

It is because the container (motion) division is getting enlarged

I wasn't sure why until I looked it over. In IE 6 and earlier, fixed positioning isn't available so the container must be resized and repositioned along with the fly out's motion or else you get a scroll bar or can't see the entire menu. I had this worked out at one point but then became dissatisfied with the old script's limitation on menu widths being multiples of ten. After I worked that out, I forgot about poor old IE 6 and earlier. It (they) needed a little extra code to put everything 'right' again for the right menu when it moved back completely to its resting position. Incidentally, this was also a problem in all browsers if they were (optionally) using the absolute positioning on the right menu. Fixed for all in the new mmenu.js file I just uploaded.

[ddadmin]

Just an update. I've updated the .js files per the above, plus the demos' looks slightly to suit my taste. The description is somewhat done, though none of the instructions yet.

Inside menuItems.js, one small error in the documentation:

menupos:'top',         // set side that menu slides in from (right or left)

It should be (right or left or top).

[ddadmin]

Ok, the script is almost ready to go: http://www.dynamicdrive.com/dynamicindex1/omnislide/ I'll await your final input before posting it to DD. Thanks!

[djr33]

Safari bug-- I get a trail of lines representing the top edge of the menu as it slides back. It's like: | | | | | ..... as wide as the menu is, about that much space between them.
It happens with the top and left menus, not the right aligned one, oddly enough.
This could relate to a memory issue, but I'll note that I have a top of the line mac, or at least it was a year or two ago. 2ghz dual processors, 2gb ram, etc.

[tech_support]

Ok, the script is almost ready to go: http://www.dynamicdrive.com/dynamicindex1/omnislide/ I'll await your final input before posting it to DD. Thanks!

Don't you usually put in Author visit the forums or something like that?

[jscheuer1]

Ok, the script is almost ready to go: http://www.dynamicdrive.com/dynamicindex1/omnislide/ I'll await your final input before posting it to DD. Thanks!

I flew into Berkeley earlier today, or was it yesterday? Depends upon which zone you use at this point so, I am a little lagged. I've just finished going over things and it looks very nice. I especially liked:

'As you can see, if you need a slideout menu, Omni Slide is your guy!'

As I say, the demo page looks good, we can always tweak if necessary but, I think it's a keeper. When I get some more time, I would like to make up a few more demos so folks could take a 'tour'.

I am a little concerned about djr33's experience with Safari but, mostly just surprised that it works at all with Safari as, I have no way of developing for that browser. We aren't claiming functionality in that browser but, perhaps we should say it is tolerated in Safari though not fully compliant with it.

[djr33]

It seems to work just fine with Safari. Not sure what's wrong with the graphics, but that's the only issue... just trailing lines from the top of the menu.


Note: I was in Berkeley this weekend too. My main stop was the UC library... perhaps we ran into each other if that was your purpose as well.