182348 - Mozilla 1.2 - innerHTML on a dynamically created dom node fails

Status: RESOLVED FIXED

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

Description

[Doron Rosenberg (IBM)]

Testcase: http://www.nexgenmedia.net/evang/1.2testcase/basic.html

Note that this is fixed on trunk - letting mozilla.org decide if this is
important or a wontfix.

Comment 1

[Doron Rosenberg (IBM)]

Note that this is windows only

Comment 2

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

Any idea when this broke?  Was it a build problem with the final builds?  It
seems very odd that it's Windows-only.

Comment 3

[Doron Rosenberg (IBM)]

example url: sony.com

Comment 4

[Susie Wyshak]

This needs to get fixed. Marked topembed.

Comment 5

[Doron Rosenberg (IBM)]

This is also broken on the nov. 25th 1.2 branch build for windows, so doesn't
seem to be a bad build.

Comment 6

[Peter Van der Beken [:peterv]]

See also (1.2-only) bug 182282 about document.write

Comment 7

[Clemens Dorda]

Attachment: Demo demonstrating when the bug appears

This little demo shows that the described bug apperas only if you assign a
string to the innerHTML-property of a DOM node before this node was inserted
into the document tree. If you **** a string to the nodes's innerHTML
property after inserting it into the document tree, all is working fine.
Note: Ive noticed this problem since Mozilla 1.2, Mozilla 1.1 hadn't this
problem

Comment 8

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

I can reproduce this in my trunk (gcc 3.2.1 Linux) build by making the same
mistake that is on the 1.2 branch and described in bug 167493 comment 21.

Comment 9

[michael bystrom]

I can confirm this on Macintosh too. 

Trying a workaround for bug: http://bugzilla.mozilla.org/show_bug.cgi?id=182626
I also noticed that if you put a character entitie like a dot [.] before the
string content it will render correct.

innerHTML(".<div....

just so you know

Comment 10

[David Baron :dbaron: (⌚️UTC-5, 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.