[Top][All Lists]

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

Re: lynx-dev COL/COLGROUP (was Re: more TRST support...)

From: Leonid Pauzner
Subject: Re: lynx-dev COL/COLGROUP (was Re: more TRST support...)
Date: Fri, 5 Nov 1999 01:45:37 +0300 (MSK)

4-Nov-99 15:11 Klaus Weide wrote:
> On Thu, 4 Nov 1999, Leonid Pauzner wrote:

>> 26-Oct-99 21:04 Klaus Weide wrote:
>> > * adds alignment inheritance from COLGROUP / COL / THEAD / TFOOT / TBODY.
>> With dev14 alignment inheritance from COLGROUP/COL is not complete:
>> COLGROUP have an attribute 'span' with a numeric value

> Yes

>> and COL have an attribute 'repeat' with another numeric value

> No, not in HTML 4.  What table specification are you using?

   Linkname: HTML 4.0 Specification

Hmm... That was a Proposed Recommendation which was hosted on my hard drive
for a while. Apparently, it was "work in progress" and had too many errors.
I hadn't thought that attribute names may be changed by mistake here -
HTTP/1.1 was much more accurate in its series of 6 drafts before the final RFC.
Thank you for a hint, I got the recent revision.

> COL has an attribute 'span' in HTML 4.

>> of the similar functionality as above - both are ignored currently.

> The COLGROUP's 'span' is ignored when it should, according to HTML 4:
> See <>:

>    span = [242]number [243][CN]
>           This attribute, which must be an integer > 0, specifies the number 
> of columns in a
>           column group. Values mean the following:
>           [...]
>           User agents must ignore this attribute if the [248]COLGROUP element 
> contains one or
>           more [249]COL elements.

I withdraw my report.

My (wrongly written) example had unclosed <COLGROUP> element
so the next coming <COL> had an effect as specified above.

>> Without span/repeat attributes the default value assumed to 1
>> according to HTML4.0 spec (and this is the ONLY available behaviour
>> now in lynx).

> I believe so far that it is working as it should.  That is, according
> to HTML 4.  If some table spec says something different, maybe RFC XXXX? -
> well I didn't look at it.

> But I didn't compile the dev.14 yet - did something get lost?

>    Klaus

reply via email to

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