182315 - Problem with output of document.write and layout on page

Status: RESOLVED FIXED

(Core :: DOM: Core & HTML, defect)

Description

[Jean-François Doyon]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2) Gecko/20021126
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2) Gecko/20021126

The best way way to explain this is to look at it. Check the URLL provided in IE
... Now look at it in 1.2 ... You shoudl see "garbage" output on the first line
... This is output from document.write's related to the menuing system, which
you can observe working by mousing over most items in the left navigation bar.
I'll attach a screen capture to demonstrate. This used to work fine in 1.1 ...
Also I did a COMPLETE uninstall and re-install, inculding clearing the registry
(I've had problems when going the upgrade path before) ... The problem remains.

Reproducible: Always

Steps to Reproduce:
1. Visit the URL, look at the page, that's it!
2.
3.

Actual Results:  
The JavaScript that renders the menu's (A whole lot of document.write's, I know,
it's ugly) seems to mis-behave ... The first layer is not displayed properly ...
This could be because of the order in whcih javascript/rendring occur ... But
that's just my guess :)

Expected Results:  
Visit the same URL in IE 5+ ... You'll see the expected output, basically what
used to appear in 1.1 ...

Comment 1

[Jean-François Doyon]

Attachment: Screenshot of problem

Screenshot showing the problem from my point of view. Note the very top of the
page ... That shouldn't be there, that's acutally the content of a layer.

Comment 2

[HARUNAGA Hirotoshi]

WFM on 2002112608-trunk/Mac 9.2.2.

Comment 3

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

This is 1.2-branch only.  See bug 182500.

Comment 4

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