you wil find the latest version of the HierMenus 4.0.13
This is the most widely used DHTML hierarchical menu library
and worked perfectly with Mozilla 0.9.2
Must be some kind of regression.
If you move the cursor over a blue-link then the pop-up menu appears
at the top of the browser-window instead of beside the menu-item.
Don't know what this means to other DHTML functions, which
could be affected by the regression.
Used build 2001071214
Over to evangelism, I bet this is due to the fix that went in for bug 81290,
that fix makes mozilla work more like IE does wrt .offsetXXX (which this page
uses extensively) and now this site relies on the old broken mozilla behavior
that was fixed. Markus, that change went in on 6/29, could you test builds
around that date to verify?
Bob, I recommend marking P1 because this is a really important "dhtml" library.
jst, is there a way to tell the folks at hiermenus what changed in offset*
exactly? since they just released a new version (a few weeks ago), I doubt they
will like it not working with NS6.1
Fabian, .offsetXXX changed to match what IE returns when used on positioned
elements or children of positioned elements, i.e. offsets on an element that's a
child of a positioned element are relative to the closest positioned parent,
among other things like that...
contacted via firstname.lastname@example.org 7/13/01
Yes, the problem is due to .offsetTop and .offsetLeft.
The following html demonstrates the problem:
<div id="test" style="left:100px;top:100px;position:absolute;">
<div id="test2" style="position:absolute;">
0.9.2 displays an offsetLeft and offsetTop of 100, but Build 2001062815 displays 0
Created attachment 42167 [details]
Peter replied and will be adapting the HierMenus to handle the changes in the
offsetXXX properties. But since he released a new version yesterday it will be a
few weeks before the next release.
adding as blocker to tracking bug 85104
All Evangelism Bugs are now in the Product Tech Evangelism. See bug 86997 for
Version 4.0.14 of the HierMenus code has just been posted at the WebReference
site that addresses this issue, and web authors are encouraged to download and
update their HM code (which now works as intended for NS6.0, 6.1, and Mozilla
builds before and after 20010726). Perhaps bug 90617 should be marked as fixed,
as this is an HM issue, and not a problem with Mozilla code.
can we close this out now and recomend an upgrade to those using
oops, ignore that :)
*** Bug 94162 has been marked as a duplicate of this bug. ***
Peter fixed HM, ->Fixed