116253 - rendering "<tt>i</tt> and" as "iand"

Status: RESOLVED DUPLICATE of bug 48376

(Core :: DOM: HTML Parser, defect, P2)

Description

[timeless]

Mozilla/5.0 (Windows; U; Win98; en-US; rv:0.9.6+) Gecko/20011219 09

find >There is a more general way of writing regexps that match many occurrences.<
The first paragraph after it is something like:
To be more precise, an atom followed by a bound containing one integer iand no
comma matches a sequence of exactly imatches of the atom. An atom followed by a
bound containing one integer iand a comma matches a sequence of ior more matches
of the atom. An atom followed by a bound containing two integers iand jmatches a
sequence of ithrough j(inclusive) matches of the atom. Both arguments must 0 >=
value <= RE_DUP_MAX (default 255), and if there are two of them, the second must
be bigger or equal to the first.

In ie, it's 
To be more precise, an atom followed by a bound containing one integer i and no
comma matches a sequence of exactly i matches of the atom. An atom followed by a
bound containing one integer i and a comma matches a sequence of i or more
matches of the atom. An atom followed by a bound containing two integers i and j
matches a sequence of i through j (inclusive) matches of the atom. Both
arguments must 0 >= value <= RE_DUP_MAX (default 255), and if there are two of
them, the second must be bigger or equal to the first. 

This is also happening for <B>i</B>. I'm marking this as major because it's a
serious regression.

Comment 1

[Boris Zbarsky [:bzbarsky]]

ccing harish... this sounds like a parser problem ("<tt>i</tt> and" rendering as 
"iand")

Comment 2

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

What do Dump Content and Dump Frames in viewer say?  Are they showing the right
thing.  My guess is that they will show the correct result, and that this is
really related to shanjian's checkin a few days ago.  I could be wrong, though.

Comment 3

[Hans Lawrenz]

Attachment: test case

Comment 4

[Hans Lawrenz]

Attachment: test case 2

This test case contains the first test case I posted plus two things I noticed
while making the first test case.

Comment 5

[Boris Zbarsky [:bzbarsky]]

Just poking quickly at the DOM with Inspector...  The #text node inside <tt>
contains only 'i'.  The #text node that's the nextSibling of the <tt> node
contains 'and '.  So the space between </tt> and 'and ' got dropped by the
parser and is not in the DOM.

Over to parser based on that.

Note that this is invalid markup that Harish has mentioned he may not bother
trying to handle...

Comment 6

[Daniel Wang]

*** This bug has been marked as a duplicate of 48376 ***