182268 - Side menu does not come up, javascript alert window warns of error

Status: RESOLVED FIXED

(Core :: DOM: HTML Parser, defect)

Description

[patrick]

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

Just go to:
http://www.nasdaq.com/
The side menu does not render and what appears to be a javascript alert warns of
a possible error. This occurs with mozilla 1.2, mozilla 1.1 was fine.

Reproducible: Always

Steps to Reproduce:
1.
2.
3.

Comment 1

[Phil Schwartau]

*** Bug 182237 has been marked as a duplicate of this bug. ***

Comment 2

[Phil Schwartau]

*** Bug 182237 has been marked as a duplicate of this bug. ***

Comment 3

[Phil Schwartau]

Changing OS: Linux ---> All, since the duplicate bug was filed on Win98;
and marking bug confirmed due to the duplicate bug. Increasing severity
to major because of the importance of http://www.nasdaq.com/.

Note: I'm having no trouble loading the site with today's trunk build
on WinNT. Just seems to be a bug with the 1.2 builds. If anyone has evidence
to the contrary, remove the note I'm adding to the Status Whiteboard above.

Note there have been other 1.2-specific bugs lately; for example
bug 182317, "JavaScript menu on page doesn't appear"

Comment 4

[Phil Schwartau]

Also note this 1.2-specific bug:

bug 182253 "document.write() eats initial characters in 1.2"

That might even be the cause of the current bug, if the site is 
using document.write() to create the menu items -

Comment 5

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

See bug 182500.  (I think there's another dependency of that bug referring to
http://www.nasdaq.com/ .)

Comment 6

[Matthias Versen [:Matti]]

*** Bug 182466 has been marked as a duplicate of this bug. ***

Comment 7

[Phil Schwartau]

Reassigning to Parser component for parity with bug 182500 -

Comment 8

[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.