Closed
Bug 69246
Opened 24 years ago
Closed 24 years ago
Does not properly display 2nd line of menu at Uptimes.net
Categories
(Tech Evangelism Graveyard :: English US, defect)
Tracking
(Not tracked)
People
(Reporter: jerryrowe, Assigned: bc)
References
()
Details
(Whiteboard: [due to minor coding error at the site])
Attachments
(2 files)
When the mouse is over "Stats" on the first line, the 2nd line should have
"personal" as the rightmost item. Instead it displays "login".
The status line at the bottom does show that 'personal' is the choice and
activates the correct choice.
Comment 1•24 years ago
|
||
This is due to a slight mistake in the HTML at the site.
The site uses good browser-sniffing and detects Mozilla/N6 successfully:
var ns4 = (document.layers) ? 1:0;
var ie4 = (document.all) ? 1:0;
var w3dom = (document.getElementById && document.getElementsByName);
if (ie4) w3dom = 0;
if (ns4) w3dom = 0;
However, compare the NS4, IE4, and Mozilla codepaths for the MouseOver event:
function hi2(layer,imgnr)
{
if (w3dom) {document.getElementsByName("img" + layer + imgnr).item(0).src =
eval("img" + imgnr + "on.src"); }
if (ns4) {document.layers["menu"+layer].document["img" + layer + imgnr].src =
eval("img" + layer + imgnr + "on.src"); }
if (ie4) {document.all["menu" + layer].document["img" + layer + imgnr].src =
eval("img" + layer + imgnr + "on.src"); }
}
Notice the "w3dom" branch has: eval("img" + imgnr + "on.src")
but the "ns4", "ie4" branches have: eval("img" + layer + imgnr + "on.src");
This means that in Mozilla, the wrong image is retrieved for the highlight.
For example, the "Personal" element mentioned by the reporter is as follows:
<a href="bottom.html?show=spersonal" target="bottom" onMouseOver="hi2(2,4);"
etc.
When hi2(2,4) is called, NS4 and IE4 are directed to fetch "img24on.src"
But Mozilla is directed to fetch "img4on.src", which is a "login" gif.
OS: Windows NT → All
Comment 2•24 years ago
|
||
Comment 3•24 years ago
|
||
If you try the reduced HTML testcase above, you will see the problem the
reporter describes. However, there are no errors in the JavaScript Console.
Furthermore, if you save the testcase locally, and correct the mistake
described above, Mozilla functions the same as NS4 and IE4.
I'm reassigning this to Browser-General: what do we do in a case like this?
The HTML at the site does not make improper use of layers, and the
browser-sniffing is perfectly correct. It's just a very small coding error...
Would this go to the Evangelism component? Thanks -
Assignee: rogerl → asa
Component: Javascript Engine → Browser-General
QA Contact: pschwartau → doronr
Whiteboard: [due to minor coding error at the site]
Comment 4•24 years ago
|
||
Comment 5•24 years ago
|
||
Try either testcase in NS4, IE4, and Mozilla and see the difference.
With the dynamic testcase, you can manually correct the coding error
(in the Mozilla case) by going to the textboxes and replacing
"img4on.src" with "img24on.src",
"img4off.src" with "img24off.src"
(Only for Mozilla; in NS4 and IE4 the correct images are loaded alreay -)
Hit the "Execute" buttons to see the effect -
Comment 6•24 years ago
|
||
over to evangelism. would be nice to help since they're trying to do the right
thing.
Assignee: asa → evangelism
Status: UNCONFIRMED → NEW
Component: Browser-General → Evangelism
Ever confirmed: true
QA Contact: doronr → zach
Comment 7•24 years ago
|
||
Reassigning evangelism bugs to bclary@netscape.com.
Assignee: evangelism → bclary
Assignee | ||
Comment 8•24 years ago
|
||
*** This bug has been marked as a duplicate of 66202 ***
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → DUPLICATE
Comment 9•24 years ago
|
||
Verifying. Its really a RESOLVED FIXED, but it is not worth the spam.
Status: RESOLVED → VERIFIED
Assignee | ||
Comment 10•24 years ago
|
||
All Evangelism Bugs are now in the Product Tech Evangelism. See bug 86997 for
details.
Component: Evangelism → US English
Product: Browser → Tech Evangelism
Version: other → unspecified
Updated•10 years ago
|
Product: Tech Evangelism → Tech Evangelism Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•