151975 - Unclosed anchor in control not recognized

Status: RESOLVED DUPLICATE of bug 231631

(Core :: DOM: HTML Parser, defect)

Description

[Alastair]

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.1a) Gecko/20020611
BuildID:    2002061104

I have just experienced a problem on a forum site. The site (which uses PHPBB
bulletin board system) allows you to submit posts via a multiline edit box. It
also allows you to later edit your posts by presenting a form pre-loaded with
your original entry. I found that by submitting a post with an html anchor tag
in the multiline edit box with unclosed parenthesis around the href, but
otherwise correct, that on editing the post Mozilla would incorrectly append the
remaining HTML of the edit page into the multiline edit box in the form.

i.e. if the edit form code looked like this:

Top of page
Form start
Edit box (containing original post with href)
Form end
Bottom of page

Mozilla, upon encountering the unclosed href, would interpret it as this:

Top of page
Form start
Edit box (containing original post with href + Bottom of page)

Because the sumbit changes and delete buttons were in the html at the bottom of
the page, they were not displayed as they had been read into the edit box in raw
html instead, and so I had to go into IE6 to delete the offending content.

It seems the edit box is parsing html elements? surely thats not right...


Reproducible: Always
Steps to Reproduce:
1.Go to the above forum
2. Create a post including an valid anchor tag but with unclosed parenthesis
around the href (""'s)
3. Try to go back and edit your post.

Actual Results:  See description

Expected Results:  The edit box should not have parsed the html

Comment 1

[rods (gone)]

need testcase

Comment 2

[Alastair]

Attachment: A simple html page explaining how to recreate/test the issue

Save and view the attachment in Mozilla, initially it is displayed correctly.

Next edit the html source and remove the closing parenthesis on the href (the
closing " after the url) then save and reload the page.

Comment 3

[Boris Zbarsky [:bzbarsky]]

Parser. This is the usual problem with people not escaping stuff in <textarea>
that really needs to be escaped....

Comment 4

[Josh Birnbaum]

Duping forward in time, to a bug with a lot more discussion.

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