49030 - extra ">" added to unclosed tags.

Status: RESOLVED DUPLICATE of bug 70918

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

Description

[Jens-Uwe]

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux 2.2.14 i686; en-US; m18) Gecko/20000814
BuildID:    2000081420

the web page looks like garbage
it seems the width of some frames is too small.


Reproducible: Always
Steps to Reproduce:
1.go to www.handyshop.de and wait a moment.
2.look at the screen
3.

Actual Results:  looks strange

Expected Results:  should look good

the html code of the page seems to be messy

Comment 1

[Paul McGarry]

Just CC'ing myself cos I want to see comments on the frameset html ;) Frankly
I'm astounded that NS4.7 renders it as well as it does. It must be making some
pretty lucky guesses.

Comment 2

[Jesse Ruderman]

the page has three things that look like this:

<FRAME src="blue_01.htm"
       <FRAMESET cols="*,100,*" rows="*" frameborder="no" border="0" 
framespacing="0" scrolling="no">

closing the FRAMEs and removing the FRAMESETs makes both browsers display it 
like ie 5 (looks nice), and just closing the FRAMEs makes both browsers display 
it like moz (looks ugly).  i don't know which behavior is more correct for the 
original page.

Comment 3

[Jesse Ruderman]

Attachment: demonstration of what seems to be a parser problem: <b homer=""<i> donuts

Comment 4

[Jesse Ruderman]

confirming and sending to parser.

moz 2000081908 on win98 makes the donuts bold and italic in the above testcase, 
whereas ie 5.5 and netscape 4.75 just make them bold.

when i view-source in moz, i see a > where there isn't one.  should this be a 
separate bug?

Comment 5

[Jesse Ruderman]

if you fix the frames and then look at the page with mozilla, bug 37656 is 
visible in the center frame.  (completely unrelated to this bug, just saying 
this to avoid getting a dup report of bug 37656)

Comment 6

[Kevin McCluskey (gone)]

Dividing up claytons bugs to triage.

Comment 7

[rods (gone)]

sounds like a parser bug/content sink bug - reassigning

Comment 8

[harishd]

This is total wackyness in the document.  I think this bug is a "nice to fix"
but not a "must fix".  Marking it FUTURE.

Comment 9

[Jesse Ruderman]

Yes, it's wacky, but I think it's important that at least the view-source part 
of this bug be fixed.  Clearing "future" milestone.

Comment 10

[harishd]

Nope, not a high priority at this stage of the project. We have more important 
things to fix. Sorry. Have to mark this bug FUTURE.

Comment 11

[Jens-Uwe]

seems to work fine with the build 20001022 for Linux.
Can someone mark this as FIXED?

Comment 12

[Jesse Ruderman]

http://www.handyshop.de/ has fixed the problem, but Mozilla still screws up 
when viewing and view-sourcing the testcase.

By the way, should the view-source thing be a separate bug?

Comment 13

[Boris Zbarsky [:bzbarsky]]

the view source bug here is also bug 70918.  If that is dupped against this,
please change the summary of this to reflect the fact that it is a view source bug.

Comment 14

[Andreas M. "Clarence" Schneider]

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

Comment 15

[Christopher Hoess (gone)]

Reopening 57724 dependencies for independent resolution.

Comment 16

[Christopher Hoess (gone)]

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