- From: Al Gilman <Alfred.S.Gilman@IEEE.org>
- Date: Mon, 30 Apr 2007 08:21:31 -0400
- To: "Charles McCathieNevile" <chaals@opera.com>, wai-xtech@w3.org
At 10:31 AM +0200 30 04 2007, Charles McCathieNevile wrote: >On Sat, 28 Apr 2007 17:59:33 +0200, Al Gilman ><Alfred.S.Gilman@IEEE.org> wrote: > >... >> I want to claim failure. I'm just not developing my script skills >>fast enough. >> So I am going to describe an approach in words and see if someone else >> cares to a) explain why it won't work or b) show that it does with >> a working example. >> >> First, why? >> >> It arose out of the idea of a "tree grid." This is a common feature. It >> is something where there are several columns of information but the >> rows are grouped and show or hide as groups are expanded or collapsed, >> as indicate by the state of a row head cell (and the expand/collapse >> control in that cell). >> >> One can do this with a tree of DIVs and layout that emulates a table. >> >> But you can't do it with the group-using tree structure and HTML tables >> for the table layout (even if the data makes sense as a data table) >> because you can't slip the <div role="wairole:group"> around groups of >> <TR> elements. One could support >> a single level of expand/collapse function with <tbody role="wairole:group"> >> but then you can't nest those. >... > >Just in passing, isn't this what the scope and axis stuff in HTML 4 >is meant to provide? Yes. The intent was similar. If @scope took IDREFS as its value and @axis took IDREF these could show the necessary connections. But they don't. And I haven't thought about how this would go for trees structures not embedded in tables. Al > >cheers > >Chaals > >-- > Charles McCathieNevile, Opera Software: Standards Group > hablo español - je parle français - jeg lærer norsk >chaals@opera.com Try Opera 9.1 http://opera.com
Received on Monday, 30 April 2007 12:21:43 UTC