Closed
Bug 182348
Opened 22 years ago
Closed 22 years ago
Mozilla 1.2 - innerHTML on a dynamically created dom node fails
Categories
(Core :: DOM: Core & HTML, defect)
Tracking
()
RESOLVED
FIXED
People
(Reporter: doronr, Assigned: jst)
References
()
Details
(Keywords: topembed)
Attachments
(1 file)
1.31 KB,
text/html
|
Details |
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.
Reporter | ||
Comment 1•22 years ago
|
||
Note that this is windows only
Any idea when this broke? Was it a build problem with the final builds? It seems very odd that it's Windows-only.
Reporter | ||
Comment 3•22 years ago
|
||
example url: sony.com
Comment 4•22 years ago
|
||
This needs to get fixed. Marked topembed.
Reporter | ||
Comment 5•22 years ago
|
||
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•22 years ago
|
||
See also (1.2-only) bug 182282 about document.write
Comment 7•22 years ago
|
||
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
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.
Depends on: 182500
Comment 9•22 years ago
|
||
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
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.
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → FIXED
Component: DOM: HTML → DOM: Core & HTML
QA Contact: stummala → general
You need to log in
before you can comment on or make changes to this bug.
Description
•