182317 - JavaScript menu on page doesn't appear in 1.2 build

Status: RESOLVED FIXED

(Core :: DOM: HTML Parser, defect)

Description

[Detlef Grittner]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2) Gecko/20021126
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2) Gecko/20021126

I'm using the brand new Mozilla 1.2 build.
On the page www.snakenetmetalradio.com should be a java script menu below the
add banner. But there are only some characters misplaced in the upper left corner.
The menu was visible and working with Mozilla 1.2b and 1.0.1.

Reproducible: Always

Steps to Reproduce:
1.
2.
3.

Comment 1

[Phil Schwartau]

Reassigning to Browser-General until we can get further info. Menu code at:
view-source:http://www.snakenetmetalradio.com/includes/snmenus/snmenus.js

Detlef: are you seeing any errors in 
Tools > Web Development > JavaScript Console?
(be sure to clear it of any previous errrors first)

Comment 2

[Detlef Grittner]

Yes, I see several errors.
I have copied them from the JavaScript Console:

Error: m has no properties
Source File: http://www.snakenetmetalradio.com/includes/snmenus/snmenus.js
Line: 24

Error: syntax error
Source File: http://www.burstnet.com/cgi-bin/ads/ad3953a.cgi/RETURN-CODE/JS/1158
Line: 1
Source Code:
<SCRIPT>

Comment 3

[Phil Schwartau]

Gee, this site WORKSFORME using builds from today, 2002-11-27,
on both Linux and WinNT. The menu appears correctly, and I get
no errors in the JavaScript Console. 

Since Detlef's build is from yesterday, I wonder if this was
a one-day regression.

Detlef:

1. The menu says, "Listen - Metal Lounge - Requests-... etc.", right?
2. Could you try a build from today and see if that works?
3. If not, could you try a new Mozilla profile? 

You can force the Profile Manager to come up (if it doesn't already)
by launching Mozilla from a console as follows:

       [(path to Mozilla)] ./mozilla -profilemanager

When the Profile Manager comes up, click on "New Profile" and
see if that helps. Of course, if today's build works OK, you 
won't need to try a new profile -

Comment 4

[Andrew Schultz]

Phil: he's using 1.2 release rather than yesterday's trunk build.

I see this bug with 1.2 release for linux, but worksforme with linux trunk build
20021126

Comment 5

[Phil Schwartau]

Andrew: thanks, you're right. My useragent string from the trunk build is
Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.3a) Gecko/20021127

Confirming bug based on Andrew's findings -

Comment 6

[David Baron :dbaron: (⌚️UTC-4, no longer working on Mozilla)]

Is the problem on http://www.snakenetmetalradio.com or
http://www.snakenetmetalradio.com/default.asp ?  I don't see an ad banner in the
former, and the latter crashes my copy of Mozilla, so I can't tell if this is a
dependency of bug 182500 or not.  I suspect it is, though.

Comment 7

[Andrew Schultz]

yes, the actual problem is at http://www.snakenetmetalradio.com/default.asp

the crash might be flash-related.  You might be able to test the page by
removing flash or upgrading to flash 6 beta.

Comment 8

[David Baron :dbaron: (⌚️UTC-4, no longer working on Mozilla)]

Yep, the crash was plugin-related, and this is an instance of bug 182500.

Comment 9

[Phil Schwartau]

Reassigning to Parser component for parity with bug 182500 -

Comment 10

[David Baron :dbaron: (⌚️UTC-4, no longer working on Mozilla)]

I have tested that this bug was an instance of bug 182500 / bug 182253 based on
comparison of two Linux builds compiled with gcc 3.2.  This bug was present in
the 1.2 release and was the only bug fixed in the 1.2.1 release (and the reason
for the 1.2.1 release).

Marking this bug as fixed since it should be fixed in the 1.2.1 release.