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)

x86
Windows NT
defect

Tracking

()

VERIFIED FIXED

People

(Reporter: gemma, Assigned: harishd)

References

()

Details

(Whiteboard: [TESTCASE])

Attachments

(1 file)

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
Assignee: troy → ekrock
The page seems to try and determine whether the app is IE or Navigator and then
generates different HTML
Attached file Testcase
Whiteboard: [TESTCASE]
Assignee: ekrock → karnaze
Summary: wrong layout → [4.xP] comments generated by document.write() within TABLE not parsed correctly?
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! ;->
Assignee: karnaze → harishd
Harish, the content model is not correct.
Target Milestone: M13
*** Bug 22748 has been marked as a duplicate of this bug. ***
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
FIXED.
Fixed in the Jan 20th build.
Status: RESOLVED → VERIFIED
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.

Attachment

General

Created:
Updated:
Size: