W3C home > Mailing lists > Public > public-html@w3.org > September 2008

Re: function and impacts (was: @scope and @headers reform)

From: James Graham <jg307@cam.ac.uk>
Date: Thu, 25 Sep 2008 14:10:28 +0100
Message-ID: <48DB8DC4.3050804@cam.ac.uk>
To: Gez Lemon <gez.lemon@gmail.com>
CC: W3C WAI-XTECH <wai-xtech@w3.org>, public-html@w3.org, Ben 'Cerbera' Millard <cerbera@projectcerbera.com>

Gez Lemon wrote:
> 2008/9/25 James Graham <jg307@cam.ac.uk>:
>>> Nested headers aren't allowed at the moment, but if they are allowed
>>> later, how would the automatic associations for a th in the middle of
>>> a table work?
>> I have (in conjunction with others) put forward a detailed proposal for this
>> which is available *in the form of running code* [1]. DO you have any
>> suggestions for improving it?
>>
>>
>> [1] http://james.html5.org/tables/table_inspector.html
> 
> I changed an example to use nested headers [1], and run it through the
> table inspector. The table inspector reports "Budgeted", "Actual", and
> "Forecasted" as headers for the data in the columns "TCO", "ROI", and
> "NPV". That's not correct. The automatic association has assumed the
> headers run to the end of the row.

That suggests that the automatic association should only occur if the header has 
the a row/colspan (depending on the direction we are looking along) that is 
greater than or equal to that of the cells it is being associated with. We 
should see if this is a more general phenomenon that applies to a wide class of 
tables.

In general, it would be good to look at more tables than this one example, 
otherwise we risk optimizing the language design for this special case to the 
detriment of all other cases.

-- 
"Eternity's a terrible thought. I mean, where's it all going to end?"
  -- Tom Stoppard, Rosencrantz and Guildenstern are Dead
Received on Thursday, 25 September 2008 13:11:03 UTC

This archive was generated by hypermail 2.3.1 : Monday, 29 September 2014 09:38:58 UTC