Same with 2002041711/RC1/Win2K, but IMHO is bug on site developer's side. In MSIE5.0 is page rendered correctly.
I see this too (RC1, wXP) and actually the JS looks ok. and what makes me think that mozilla is to blame is, that maximizing the window or even resizing by 1 pixel yields the ought-be correct result accepting bug, chaning to normal, proposing mozilla1.0 JS used: <img src="png/krone.png" style="position:absolute;top:23px;left:289px;visibility:hidden;" width="15" height="10" border="0" alt="" id="kontakt"> <a href="kontakt.html"><span style="position:absolute;top:33px;left:285px;width:70px;height:28px;" onMouseOver="document.getElementById('kontakt').style.visibility = 'visible'" onMouseOut="document.getElementById('kontakt').style.visibility = 'hidden'">
Severity: major → normal
Status: UNCONFIRMED → NEW
Ever confirmed: true
Reassigning to Layout; cc'ing Boris in case this is a known CSS positioning problem. I will attach reduced testcases below -
Assignee: rogerl → attinasi
QA Contact: pschwartau → petersen
Using Mozilla binaries 20020415xx on WinNT, Linux, Mac9.1 Both testcases work fine on Linux, Mac. But on WinNT, the mouseovers produce strange results. The second testcase works better: only the "Modelle" mouseover gets corrupted.
Summary: Strange graphic-errors on page above → Strange layout errors on mouseovers
Changing QA Contact
QA Contact: petersen → moied
Works fine for me using 2002050108 build on WinXP. email@example.com: Can you test this using WinNT?. Thanks.
Target Milestone: --- → Future
I made some more tests with Windows 98. In Mozilla RC1 the error still appears. In the current nightly (2002050108), it no longer appears. So it seems that it is fixed now. Can others confirm this?
WFM using mozilla build 20020508 on WinNT and Linux.
I used mozilla Trunk builds in Comment #10.
The bug was away in some nightly-builds, but it is back in RC2!!
WFM, 2002-08-24-04 trunk Linux WFM, 2002-08-24-04 trunk Windows 2000
This is fixed with 1.1, so anyone who has acces to it please close it.
Um... you reported the bug. So you have permissions to resolve it any time you want....
Status: NEW → RESOLVED
Last Resolved: 17 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.