Closed Bug 282152 Opened 20 years ago Closed 15 years ago

Tables not rendering correctly

Categories

(Core :: DOM: HTML Parser, defect)

defect
Not set
normal

Tracking

()

RESOLVED WONTFIX

People

(Reporter: mikronh, Unassigned)

Details

Attachments

(2 files)

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0

Can only give a clear example : try the site below in IE & Firefox and see the
difference for yourself.

http://www.bingoal.net/CONTENU/NLtableBEL1.shtml


Reproducible: Always

Steps to Reproduce:
1.Access the site with IE
2.Access the site with FireFox
3.See the difference
Assignee: firefox → nobody
Component: General → Layout: Tables
Product: Firefox → Core
QA Contact: general → layout.tables
Version: 1.0 Branch → Trunk
The HTML code of that page looks strange with tags like <DATEMA> and <RESULTAT>.
Maybe they use something specific to IE.
> 1.Access the site with IE

No can do; no IE anywhere near here... can you post a screenshot of what IE shows?
(In reply to comment #2)
> > 1.Access the site with IE
> 
> No can do; no IE anywhere near here... can you post a screenshot of what IE shows?

Here's how IE renders it : http://www.buffalo.easynet.be/Render0000.jpg
Does IE get sent the same source?  There are </tr> tags in that page that IE
seems to be ignoring, if it renders the way that screenshot shows...
IE gets sent the same source.

There are 24 tr opening tags, and 123 tr closing tags...
(In reply to comment #5)
> IE gets sent the same source.
> 
> There are 24 tr opening tags, and 123 tr closing tags...

if you replace the extra </tr> tags (the ones that should be </td>) with
</td></tr> then IE renders it the same way as firefox... IE seems to be
interpreting what "should" have been written, rather than what is written.
Dan, do you mean replacing "</tr>" with "</td></tr>", or do you mean replacing
"</tr></tr>" with "</td></tr>"?

Note that in HTML "</td>" is optional, so "</tr>" and "</td></tr>" are the same
thing.
I did not know that..., but yes, replacing the lines that are written as
<td class="CED">21.05  </tr>
with
<td class="CED">21.05  </td></tr>
causes IE to display the same as Firefox, "buggy", while
replacing the above line with
<td class="CED">21.05 </td>
or
<td class="CED">21.05
caused Firefox to display it the same way that IE does normally.  If you read
the source it looks like the extra </tr> tags are supposed to be </td> tags,
whoever wrote the table doesn't really want a new table row there, they just
want a new table data.  Firefox reads the </tr> tag and starts a new row, while
IE waits for the <tr> tag to actually start the new row.
  The table is poorly written, but if firefox waited for that <tr> tag to
actually start its new table row, then it wouldn't display poorly.
Attached file Minimalish testcase?
Dan, does IE render this with just three rows?
In any case, clearly not a layout issue.  Blake, want to try to figure out what
IE's behavior wrt to optional table element end tags is, exactly, and whether
this one page is enough reason to try to duplicate its bugs?
Assignee: nobody → parser
Status: UNCONFIRMED → NEW
Component: Layout: Tables → HTML: Parser
Ever confirmed: true
OS: Windows XP → All
QA Contact: layout.tables → mrbkap
Hardware: PC → All
(In reply to comment #9)
> Does IE render this with just three rows?

Yes
(In reply to comment #12)
> What about this testcase?

Same thing here, 3 rows ( http://www.jeria.net/mozilla/attachment_180590.gif )
So it sounds like IE is just violating the HTML spec (which clearly says that
"</tr>" and "</td></tr>" are exactly equivalent.....)
Right, but we might also be violating HTML spec by starting a new table row
without a "<tr>" tag.  Of course, IE is continuing the same row, even though it
ended already, "</tr>".  Which is more important, ending rows at </tr> or only
starting rows at <tr>?

Either way we go, someone will mistype their html code...
> we might also be violating HTML spec by starting a new table row without a
> "<tr>" tag. 

No, we're not.  The HTML spec explicitly says that any behavior is OK there
(that's the first point where the markup is invalid, and for invalid markup HTML
allows arbitrary behavior).
Assignee: parser → nobody
QA Contact: mrbkap → parser
WONTFIX per HTML5. If you disagree, please file a bug against the HTML5 spec in the W3C's Bugzilla.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: