[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: LYNX-DEV Tables in Lynx ...
|
From: |
nospam-seesignature |
|
Subject: |
Re: LYNX-DEV Tables in Lynx ... |
|
Date: |
Wed, 1 Apr 1998 15:35:18 -0500 |
On Wed, 1 Apr 1998, Jan Hlavacek wrote:
> On Tue, Mar 31, 1998 at 03:01:06PM -0500, address@hidden
> wrote:
> > Actually it is much harder than it looks. Mainly because people abuse
> > table tags more than most other HTML, e.g. what do you do if there are
> > only 5 <TD> entries on one line and 7 in the next? What about missing
> > </TABLE> tags? Or even missing </TR> (<TR><TD>...<TD>...[implied
> > /TR]<TR><TD> is a very common abuse).
>
> Actually, this is not an abuse. The </TR> is optional:
> <!ELEMENT [371]TR - O (TH|TD)+ -- table row -->
>
> Also, I don't think there is anything in HTML DTD that would prevent
> you from having different number of cells in different rows. It may not
> make much sense, but IMHO it is legal. And if you display table as
> numbered list, all you get is just extra items in some "rows", no big
> deal.
Implementing these things is still difficult. A better example (what I
was trying to remember):
<TABLE> Some text outside any row
<TR> Some text outside any table date <TD> column 1 </TD> more outside
text <TD>...</TR> out of row text <TR>...</TR> More extraneous </TABLE>
And the extraneous often has form or anchor or <P> or <BR> or other
interesting tags.
What the GUI browsers do is that <TABLE> acts like a nested <BODY> tag, so
you get a new (nested) rectangular sub-area to start rendering in and the
TD and TR tags create dividers in (singly nested) rectangular sub-areas.
They make a few passes to attempt to optimize the widths and heights, but
it is even nasty for them.
--- reply to tzeruch - at - ceddec - dot - com ---