Closed Bug 11141 Opened 25 years ago Closed 25 years ago

QA BLOCKER {sink} document.write fails to write HTML tags

Categories

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

defect

Tracking

()

VERIFIED FIXED

People

(Reporter: gerardok, Assigned: vidur)

References

Details

(Whiteboard: TESTCASE)

Attachments

(2 files)

Overview Description: Document.write fails to write HTML tags and any text written before the last tag. Steps to Reproduce: 1) Create a HTML file with the following content: <HTML> <HEAD> <TITLE>test.html</TITLE> </HEAD> <BODY> <SCRIPT TYPE="text/javascript"> document.write('Foo'); document.write('<BR>'); document.write('World'); </SCRIPT> </BODY> </HTML> 2) Open the file in apprunner Actual Results: Only the word 'World' is displayed. Expected Results: The words 'Foo' and 'World' displayed in two separate lines. Build ID & Platform Bug Found: 1999-07-28-15-M9 on Windows NT Additional Builds and Platforms Tested On: The same failure happens on 1999-07-28-15-M9 on Linux, and on 1999-07-28-14-M9 on Mac Additional Information: n/a
Priority: P3 → P1
QA Contact: desale → gerardok
Attached file go/no-go test case
Whiteboard: TESTCASE
On the "shipping" M8, Win98 properly showed two lines of test. I will try M9 when my build finishes. It's either (very) platform specific, or very recent.
FYI: Moving SCRIPT to the HEAD does not cause this problem. Adding myself to the CC list.
Exact same test as the 8/2 one above, on Win98, except with M9 (8/2/99 ~11Pm build). Only one line of text shows up. This bug is recent.
Assignee: vidur → peterl
Forwarding this one to Peter Linss as per our conversation. I'm surprised it actually worked with M8. The current behavior is what I'd expect with the current version of the HTMLContentSink. Peter is making large changes to the sink to fix the way we track frame creation. This should be fixed as a result of his changes.
Status: NEW → ASSIGNED
Summary: document.write fails to write HTML tags → {sink} document.write fails to write HTML tags
Target Milestone: M10
Attaching another test case, which should say: "Header", "Paragraph 1", "Paragraph 2", "Paragraph 3". (Header is a header :-). It currently only has "Paragraph 2" and "Paragraph 3" (Linux 1999-08-16-08-M9).
*** Bug 12119 has been marked as a duplicate of this bug. ***
Moving all content sink issues to M14.
Make that M14.
Client Mail/News QA, like most of QA, requires this to work in order for automatated testcases using Javascript to work. If this bug actually gets fixed it will benefit us. Par
Target Milestone: M14 → M12
Adding myself to cc: list
Severity: critical → blocker
Summary: {sink} document.write fails to write HTML tags → QA BLOCKER {sink} document.write fails to write HTML tags
Target Milestone: M12 → M11
QA needs this fixed ASAP. Moving to M11...we cannot wait until M12.
Blocks: 11349
Depends on: 15729
*** Bug 13524 has been marked as a duplicate of this bug. ***
Assignee: peterl → vidur
Status: ASSIGNED → NEW
Thanks for taking this Vidur.
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Fixed with content sink changes on 10/26.
Status: RESOLVED → REOPENED
If this bug is fixed, then why does this page, http://timb.simplenet.com/dom/ , not display correctly still? I don't think this is a matter of a site not made for mozilla 5. In fact, it is a tutorial on "doing dHTML right" the W3C DOM way. If you notice when you load it in mozilla, a whole bunch of document.write() stuff fails to be written and you can see the actual javascript on the screen at the top of the page.
Status: REOPENED → RESOLVED
Closed: 25 years ago25 years ago
It's an error in the page. The script element contains document.write("... </SCRIPT>"); That SCRIPT tag ends the script element. This is the correct behavior. It is a separate issue (has nothing to do with document.write), and is probably pretty hard to "fix", since the Mozilla parser actually works correctly. If you want this issue fixed, file a separate bug. In fact, I'll do that now just so that it can be tracked and decided upon by the people who should be making the decision.
(Forgot to mention that I re-resolved the bug there in the text.) The new bug is bug 18324.
*** Bug 14700 has been marked as a duplicate of this bug. ***
*** Bug 16278 has been marked as a duplicate of this bug. ***
Status: RESOLVED → VERIFIED
Verified on 1999-12-17-13-M12 build
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: