This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 18791 - Reducing data table size based on the row grouping, column grouping combined with the table header cell structure
Summary: Reducing data table size based on the row grouping, column grouping combined ...
Status: RESOLVED WONTFIX
Alias: None
Product: HTML WG
Classification: Unclassified
Component: HTML5 spec (show other bugs)
Version: unspecified
Hardware: PC Windows XP
: P2 enhancement
Target Milestone: ---
Assignee: This bug has no owner yet - up for the taking
QA Contact: HTML WG Bugzilla archive list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-09-06 13:31 UTC by Pierre Dubois
Modified: 2016-04-20 18:44 UTC (History)
5 users (show)

See Also:


Attachments
Javascript Table Parser (62.04 KB, text/x-javascript)
2012-09-06 13:31 UTC, Pierre Dubois
Details

Description Pierre Dubois 2012-09-06 13:31:02 UTC
Created attachment 1182 [details]
Javascript Table Parser

In the Editor's Draft 4 September 2012, there are no mention about on how the size of a data table can be reduced to being displayed better on a smaller screen, like a mobile device.

I developped two techniques (FYI - currently in draft but with the intention to be submited to the WCAG 2.0 Techniques) that describe a method on how the row grouping, column grouping combined with the table header cell structure can be used together to define data summaries. 
* http://wet-boew.github.com/wet-boew/docs/tableparser/summariesrowgroup-techniques.html
* http://wet-boew.github.com/wet-boew/docs/tableparser/colgroupsummary-techniques.html

As per my research, the data summaries is often in a smaller size than the data itself. A common example is an invoice. The "Subtotal" and the "Total" row group is often smaller than the items listed in the table. With that, the table display size can be reduced to show only the total or the subtotal and the total row group instead of listing all the item contained in the invoice. With that technique it would be possible for an user agent to provide a mechanism to colapse/expend upon user request those kind of table.

This could give the possibility for people with disability to get a global view of the data table before to read each individual data cell. 

----

Attached: A javascript table parser that takes in consideration the row group, the column group and the placement, size of the header cell to create the relationship between each cell contained in a table. You can find the most recent version here: https://github.com/wet-boew/wet-boew/blob/master/src/js/workers/parser.table.js

The following table validator use the preceding table parser.
http://wet-boew.github.com/wet-boew/docs/tableparser/validator-htmltable.html

FYI - Here a mailing sent to WAI Interrest Group about a request for comments in regards of the techniques mentioned here. http://lists.w3.org/Archives/Public/w3c-wai-ig/2012JulSep/0310.html

Thank you

:-)
Comment 1 Pierre Dubois 2012-10-01 19:14:53 UTC
See my proposal about the Table Usability Concept here: http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2012-September/037475.html

:-)
Comment 2 Erika Doyle Navara 2012-10-15 22:03:09 UTC
Moving this to HTML.next as we work to lock down HTML5.0 for CR.

For future reference, it appears that some of the broken links below can be fixed by substituting "demos" for "docs" in the path. E.g.,

http://wet-boew.github.com/wet-boew/docs/tableparser/summariesrowgroup-techniques.html

Is now at:

http://wet-boew.github.com/wet-boew/demos/tableparser/summariesrowgroup-techniques.html
Comment 3 Robin Berjon 2013-01-21 15:57:46 UTC
Mass move to "HTML WG"
Comment 4 Robin Berjon 2013-01-21 16:00:29 UTC
Mass move to "HTML WG"
Comment 5 Arron Eicholz 2016-04-20 18:44:01 UTC
HTML5.1 Bugzilla Bug Triage: 

This bug constitutes a request for a new feature of HTML. Our current guidelines, rather than track such requests as bugs or issues, is to create a proposal for the desired behavior, or at least a sketch of what is wanted (much of which is probably contained in this bug), and start the discussion/proposal in the WICG (https://www.w3.org/community/wicg/). As your idea gains interest and momentum, it may be brought back into HTML through the Intent to Migrate process (https://wicg.github.io/admin/intent-to-migrate.html).