1) molendijkGroup: Members Posts: 78Joined: 29 Nov 2005Location: The Netherlands (Groningen)IP: 84.86.--.--
Posted:
Some suggestions(?) to Angus.
The following observations concern the Cascading Popup Menus v5.2 RC3, relative to an anchor.
1) Whatever value you set for hideDelay, the sub menus will disappear too soon if they have (considerable?) overlap with higher level menus.
2) Netscape, at least some versions of it, has problems with menus-having-scrollbars (if they really get a scrollbar) in pages emulating frames, and also with hiding: the submenus don't always hide after mouseout.
Ad 1: Go to 'http://www.let.rug.nl/~molendyk/wijzigingenrugnaarwerk/zmenustwinhelixpop/'. Move the mouse over 'Twinhelix possibilities', then over 'link + open submenus', then purposely move over submenu items below it (not too slow), then move to subitems 'will stay for a while'. You will see that 'will stay for a while' does not hide before you reach it.
Doing a similar thing with 'js click actions + open submenu' will not get you in time to 'will hide too soon', because these subitems have considerable overlap with their 'parent'. Angus, has this problem been signaled to you (for the anchor version of the menu)?
Ad 2: Netscape adds a scrollbar that you don't want if you are emulating frames with the help of css+divs. You only want scrollbars for the 'fake frames' (=divs), not for the whole page. Also, and apart from that, the menus won't always disappear in Netscape after mouseout. Solutions: - overflow:hidden in the html tag (doing this for the body tag is not enough) - set hideDocClick to true.
Good luck, Arie (Molendijk).
Arie.
2) Angus TurnbullGroup: Moderators Posts: 4042Joined: 7 Dec 2003Location: New ZealandIP: 203.173.--.--
Posted:
1) Yes, whenever you mouseover an item, it begins hiding menus not in the current menu tree. The FreeStyle Menu script is newer and has a "switch timer" implementation (as well as show and hide timers) so it's more advanced in that regard ans will work the way you describe. Really, I recommend that most people use that script unless they really need cross-frame menus!
2) Some NS IFRAME issues were noted in Firefox 1.0 with the FreeStyle Menu script a while back; they don't affect Firefox 1.5. Try searching through that forum as I posted a small amount of code that fixed it for that script.