Use this area to submit an original
DHTML or CSS code for other visitors of DD to utilize or critique. Furthermore,
through this method of submission, your code may be added to DD's
DHTML or
CSS Library section if deemed
useful by the admin of DD. Guidelines for using this forum:

This forum should only be used to post an
original, fully functional and "practical" script. It is not for
putting up experimental or the rudimentary "my first script."

To submit a code, fill out the information
on your code as outlined in the instructions. For the actual code, ideally
you should just enter a URL to the full working demo, to make it easy for
others to check it out. However, if this isn't possible for you, you can
also submit your code inline on the forums, by attaching it.

If you're attaching the full code inline in
your post, please following the following conventions whenever possible:

For straightforward code, just attach it as a single .txt file

For code that consist of both code and images/other media, zip up
all the files and attach it as a .zip file

Should you need it, this forum supports file attachments of the
following type: .txt, .zip, .js, and images (.gif, .jpg, .png etc).

Again, if possible at all, it's best just to submit the URL to the
script instead, for ease of review/ critique by others.

By submitting a code, you declare that
you're the original author of the code, and grant Dynamic Drive to right
to include and modify the code for possible inclusion in our code library.

If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

In Opera 9.01 several of the effects cause the flyout to disappear and/or redraw when the mouse traverses from the trigger to the flyout. This is generally fixed by having some kind of delay onmouseout of the trigger before the flyout disappears. However, if you already have that, it probably has to do with Opera not recognizing that the mouse is over the flyout due to some style property applied to the flyout for a given effect.

Particularly bad were the two blind wipes for the horizontal menu. It also appears as though the border (or what looks like the border) of the trigger isn't considered as a part of the trigger and flyout for the purposes of determining if the mouse is still over one or the other of them.

A very ambitious menu. Looks like it shouldn't be too hard to either fix these items or disable them where they may cause problems.

I agree with John. The script looks like it has a lot of potential, but as is, it's quite rough around the edges. For example, the submenus are not completely aligned to the triggering menu item, meaning you have to carefully move your mouse over to the submenu, or it will disappear on you. The way the submenus appear is just very jittery it feels.

Please keep us posted on further developments on this menu. It definitely has a lot of potential, with a better interface, and more importantly, improved submenu behavior.

well. I updated it based on what you both said. The border is only 1px wide and I that is more of a browser issue so there was not fix for that. It was actualy intetional that they wouldn't line up so that was very easy to fix

It definitely feels more "solid" now! I noticed with the multiple level examples (>2 levels), the sub menu don't automatically disappear when the mouse leaves the submenu. Is that intentional? I'd think most people would prefer that it did.

I noticed with the multiple level examples (>2 levels), the sub menu don't automatically disappear when the mouse leaves the submenu. Is that intentional? I'd think most people would prefer that it did.

I was unable to reproduce this. What browser did you notice it in? Also was it a particular effect?

Originally Posted by mburt

There's an error on the horizontal-menu in FF though... I just tried it.

What error? The only one I am aware of is the "double border". It is less an error than an annoyance.

As to the firefox/textarea problem. I have confirmed that this is only occuring in Firefox and it also happens in Firefox 2 beta 2. I plan to make a simple script to see if the problem is something I did or a firefox bug. I'm starting to think it is a firefox bug. However, a quick search of bugzilla didn't turn up anything.