Closed
Bug 22485
Opened 25 years ago
Closed 25 years ago
[4.xP] comments generated by document.write() within TABLE not parsed correctly?
Categories
(Core :: Layout, defect, P3)
Tracking
()
VERIFIED
FIXED
M13
People
(Reporter: gemma, Assigned: harishd)
References
()
Details
(Whiteboard: [TESTCASE])
Attachments
(1 file)
533 bytes,
text/html
|
Details |
Perhaps we could get a description of what is wrong?
entire chunk of text and images shifted to the right side with only a banner and some menu text at the bottom remain in the correct position
The page seems to try and determine whether the app is IE or Navigator and then generates different HTML
Comment 3•25 years ago
|
||
Updated•25 years ago
|
Whiteboard: [TESTCASE]
Updated•25 years ago
|
Assignee: ekrock → karnaze
Summary: wrong layout → [4.xP] comments generated by document.write() within TABLE not parsed correctly?
Comment 4•25 years ago
|
||
Mats's attached test case looks fine in Nav4.7+ and IE5 but strange in M12. (All testing on WinNT 4.0 SP3.) The cause is some combination of these factors: - HTML open comment string dynamically generated by JavaScript - this occurs inside a TABLE Assigning to karnaze as this seems to be an issue of parsing tables with dynamically generated comments. But it might be a parser issue for rickg? Mats--Absolutely *killer* job of simplifying a very complex page down to a simple test case. That was a complicated page with confusing side issues. You're an animal--thanks! ;->
Updated•25 years ago
|
Assignee: karnaze → harishd
Comment 5•25 years ago
|
||
Harish, the content model is not correct.
*** Bug 22748 has been marked as a duplicate of this bug. ***
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Comment 9•19 years ago
|
||
For future clarification: this bug made the parser flush its current tokens when it encounters a <script> tag. This makes sure that content that should be tokenized with the output of a script document.write() in mind is not processed before the output is obtained. (in this case <!-- was document.written, but was being wrongly thought of as an unclosed comment because the parser had already consumed the closing -->).
You need to log in
before you can comment on or make changes to this bug.
Description
•