182253 - document.write() eats initial characters in 1.2

Status: RESOLVED FIXED

(Core :: DOM: HTML Parser, defect)

Description

[Andrzej Taramina]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2) Gecko/20021126
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2) Gecko/20021126

When you do a document.write( "string" ); in Mozilla 1.2 final, the call seems
to eat certain leading characters (like the < that starts an HTML tag).  If you
write a non-blank character first, then it does not seem to eat anything.

This is a new bug in 1.2.  1.1 worked just fine....

Reproducible: Always

Steps to Reproduce:
1.View html sample
2.Link shows as  normal text.
3. Uncomment the 2nd document.write() in the embedded javascript
4) Link now shows properly, but the extra character is also shown



Expected Results:  
Link should show properly as a clickable url.

Comment 1

[Andrzej Taramina]

Attachment: HTML file that illustrates the problem

Uncomment the second document.write() in the embedded javascript function as
well to see that normal characters are not eaten.

Comment 2

[Boris Zbarsky [:bzbarsky]]

worksforme, linux trunk build 2002-11-08-04 (post-1.2 build).

Comment 3

[Phil Schwartau]

Also WORKSFORME using today's trunk build on WinNT.

Reassigning to Browser-General, as I don't think this is a JavaScript
Engine problem. Note we've had a number of other bug reports like this,
that concern the 1.2 branch and not the trunk. For example:

bug 182317 "JavaScript menu on page doesn't appear"
bug 182268 "Side menu does not come up, javascript alert window warns of error"

I'm confirming this one on that basis. In fact, I wouldn't be surprised
if this bug is the cause of the two above -

Comment 4

[Phil Schwartau]

In fact, let me reassign this to the DOM folks, in case they can see
why document.write() is doing this in 1.2 builds, but not the trunk -

Comment 5

[Johnny Stenback (:jst)]

1.2 is done, this didn't make it. This is fixed on the trunk, so marking WONTFIX
for the 1.2 branch which we're done with.

Comment 6

[Phil Schwartau]

Actually, reopening and reassigning to Parser as a dependency of the
Parser meta-bug 182500, "[1.2 branch] parser bugs due to bug 167493".

Comment 7

[Phil Schwartau]

Reassigning to Parser as a dependency of bug 182500 -

Comment 8

[Jaagup Irve]

This should definetly be added to release notes of 1.2

Comment 9

[R.K.Aa.]

*** Bug 182802 has been marked as a duplicate of this bug. ***

Comment 10

[Jacek Piskozub]

*** Bug 182760 has been marked as a duplicate of this bug. ***

Comment 11

[David Baron :dbaron: (⌚️UTC-4, no longer working on Mozilla)]

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.