Spaces not rendered correctly from document.write() in <HEADER>

RESOLVED FIXED in M14

Status

()

P3
minor
RESOLVED FIXED
19 years ago
19 years ago

People

(Reporter: emontev, Assigned: harishd)

Tracking

Trunk
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Reporter)

Description

19 years ago
The following HTML demonstrates the bug:
<HTML>
<HEAD>
<TITLE>Space Bug</TITLE>

<SCRIPT TYPE="text/javascript">
document.write("There should be a space here-->");
document.write(" ");
document.write("<--But there is not.");
</SCRIPT>

</HEAD>
<BODY>

<br>

<SCRIPT TYPE="text/javascript">
document.write("There should be a space here-->");
document.write(" ");
document.write("<--And there is.");
</SCRIPT>

</BODY>
</HTML>

Comment 1

19 years ago
Created attachment 3551 [details]
html soource from comments as attachment

Updated

19 years ago
Assignee: mccabe → vidur
Component: Javascript Engine → DOM Level 0

Comment 2

19 years ago
Reassigning to DOM level 0 component.

Updated

19 years ago
Assignee: vidur → rickg

Comment 3

19 years ago
The document.writes just result in calls to the parser. I'm not sure why the
handling of the space is different in the HEAD versus the BODY, but if there's a
compatibility issue here, it's one in the parser.

Updated

19 years ago
Target Milestone: M14

Comment 4

19 years ago
setting target milestone.

Updated

19 years ago
Status: NEW → ASSIGNED
Target Milestone: M14 → M15

Comment 5

19 years ago
The script in the head has content that needs to get moved to the body. The
space (2nd doc.write) is seen as a legal char of the head and doesnt get moved.
Need to change process a bit in order to fix this.
(Assignee)

Updated

19 years ago
Assignee: rickg → harishd
Status: ASSIGNED → NEW
(Assignee)

Comment 6

19 years ago
Assigning to myself.
(Assignee)

Updated

19 years ago
Target Milestone: M15 → M14
(Assignee)

Comment 7

19 years ago
Fixed by updating the CNavDTD.
Status: NEW → RESOLVED
Last Resolved: 19 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.