lynx-dev
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: more TRST support (was: Re: lynx-dev another largish patch)


From: Klaus Weide
Subject: Re: more TRST support (was: Re: lynx-dev another largish patch)
Date: Tue, 26 Oct 1999 15:53:47 -0500 (CDT)

On Tue, 26 Oct 1999, Leonid Pauzner wrote:

> 26-Oct-99 08:22 Klaus Weide wrote:
> > On Tue, 26 Oct 1999, Leonid Pauzner wrote:
> 
> >> 26-Oct-99 01:48 Klaus Weide wrote:
> >>
> >> > * Added support for ROWSPAN attribute of TD and TH to TRST.  This only
> >> >   reserves the appropriate amount of space in subsequent lines.
> >>
> >> Is it possible to add support for COL/COLGROUP align= (and span=)
> >> attributes to keep inheritance with TD,TH,TR... own align= attributes?
> >>
> >> Currently COL/COLGROUP align= attribute just ignored.
> 
> >  From the comments in TRSTable.c:
> 
> > **  Missing, but can be added:
> > **  - Support for COLGROUP/COL
> > **  - [ ... ]
> 
> I saw this. I think checking of align= attr and span/repeat numbers
> is not a big problem when all elements (TABLE, THEAD?, TBODY?, TR, TD, TH)
> already understands align= attributes.

Well, COLGROUP/COL support would just have to parse the stuff, keep track
of it, and use it as yet another source for alignment setting - nothing
really exciting...

Currently nothing is done for THEAD, TFOOT, TBODY.  Actually, they cancel
TRST processing:

    case HTML_THEAD:
    case HTML_TFOOT:
    case HTML_TBODY:
        HText_endStblTR(me->text);

That's probably not necessary...  I think I just put it there until we
do something useful with those tags' attributes.  I haven't looked into
it, but probably just more boring keep-track-of-it stuff.


Anyway, such incremental improvements to TRST stuff shouldn't distract
from the fact that it isn't full table support...  Effort may be better
spent adding some fuller table support, rather than implementing obscure
ways to set alignment for TRST if those aren't used in practice anyway.

   Klaus



reply via email to

[Prev in Thread] Current Thread [Next in Thread]