- From: <bugzilla@wiggum.w3.org>
- Date: Tue, 01 Jul 2008 16:59:33 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=5822 Rob Burns <rob@robburns.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rob@robburns.com --- Comment #2 from Rob Burns <rob@robburns.com> 2008-07-01 16:59:33 --- (In reply to comment #1) > This was intentional, based on research into what tables on the Web actually > looked like and what the expected UI of headers currently is and ideally should > be. > > Basically, it turns out that while one would intuitively think that > hierarchical headers are a good design, they end up being more of a pain than a > gain. By forcing a two-level structure, we make authors who are using > headers="" think more carefully about what they want each cell to do and be in > the table. > Ian as usual you're confusing two different things here. Hierarchical headers allow one header cell to reference another header cell so that the data cells associated with the first header cell are then associated with both headers (and so on). This bug is meant to address the issue that the headers attribute sometimes needs to associate a data cell with another data cell (a TD element) that is then serving as both a data and a header cell. These are clearly areas way outside your comprehension and it would be good to ask for some help with these issues. -- Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
Received on Tuesday, 1 July 2008 17:00:08 UTC