Problems with submenus and highlighting

Poster: ukboy
Dated: Tuesday July 12 2005 - 17:24:26 BST

Hi,

Have been testing this menu with a common browser (IE6).

I have a typical arrangement for my menu: two "levels" of links on my horizontal menu, i.e. the initial links shown and then a submenu under some of those primary links. See the first example menu on the Milonic site to see what I mean.

Here's the fiddly part to explain: what I've noticed is that if you place the mouse over one of the primary links so that it changes the bgcolor and creates the submenu underneath, and then move the mouse down to highlight over the first entry of the submenu and then after a few seconds move the mouse back up to the "primary" link, the first entry of the submenu remains highlighted even though the mouse has moved away from the submenu.

This happens also with the horizontal example menus on this site, see e.g. the first example menu or the tooltips one, suggesting it's just a bug with the script itself.

Any hack/workaround for this? Or am I completely wrong in thinking this is nothing to do with my end?

Thanks in advance for any help you can offer

Poster: Ruth
Dated: Tuesday July 12 2005 - 17:57:48 BST

I'll post a notice to Milonic. Not sure if this is a fixable thing or not. I can see what it's doing. For information, the first level submenus are 'autofixed' is the only way I can think to describe it, when using a horizontal menu. The subOffsetTop=; does not apply to the first level subs with a main horizontal menu, and when you mouseOff the first item in that first level sub it's as if the mouse doesn't fire to the off setting. I tried using top="offset="; in the submenu and it will move it, but even if you offset it say by 15px [which you wouldn't want to do] if you move the mouse quickly it still doesn't fire the off setting.

Ruth

Poster: ukboy
Dated: Tuesday July 12 2005 - 18:20:33 BST

Ruth,

Thanks for your post/confirmation and offer of informing Milonic. I look forward to maybe hearing some developments about this in this thread, or maybe seeing it 'fixed' in a later version.