ISSUE-32

table-summary

how to provide a summary of a table, e.g. for unsighted navigation?

State:

OPEN

Product:

HTML 5 spec

Raised by:

Joshue O Connor

Opened on:

2008-02-07

Description:

Raised by: James Graham on behalf of Joshue O'Connor, 7 Feb 2008
http://lists.w3.org/Archives/Public/public-html/2008Feb/0124.html

Vision impaired screen reader users listen to outputted information, without any visual cues, and HTML 5 drafts up to and including http://www.w3.org/TR/2009/WD-html5-20090212/ lack a mechanism that gives an overview of complex tabular data or a brief explanation of that data.

HTML 4 provides a table/@summary attribute where authors may provide this information.

Issue is detailed at: http://esw.w3.org/topic/HTML/SummaryForTABLE 

Summary Draft Text for the Spec - Cynthia Shelly, September 14, 2009
http://dev.w3.org/html5/pf-summary/Overview.html#the-table-element
http://lists.w3.org/Archives/Public/public-html/2009Sep/0553.html

PF Advice: @Summary - Janina Sajka, June 3, 2009
http://lists.w3.org/Archives/Public/www-archive/2009Jun/0026.html

May 4, 2009 message asked Janina Sajka (WAI PF WG's new chair) for comments on several items in order to move this issue toward resolution.
http://lists.w3.org/Archives/Public/public-html/2009May/0033.html

editor's position given by ian@hixie.ch on February 24, 2009
http://lists.w3.org/Archives/Public/public-html/2009Feb/0601.html

editor's position is given by ian@hixie.ch on 2008-12-20
http://lists.w3.org/Archives/Public/public-html/2008Dec/0175.html

WAI PF WG's position is given in 6 Aug msg from Al G.
http://lists.w3.org/Archives/Public/public-html/2008Aug/0213.html
supplemented by, e.g. "Use and abuse of summary" thread
http://lists.w3.org/Archives/Public/public-html/2009Feb/0420.html
http://lists.w3.org/Archives/Public/public-html/2009Feb/0503.html
http://lists.w3.org/Archives/Public/public-html/2009Feb/0512.html

Related email:
http://esw.w3.org/topic/HTML/SummaryForTABLE#head-6fcfaa26f41088d2cf13b4dd3247225a49ee7be1

Related Bugs:
7539: Since @summary is an official part of the table element, it is no longer obsolete...
http://www.w3.org/Bugs/Public/show_bug.cgi?id=7539
7633: The use of @summary should be encouraged when circumstances warrant.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=7633

HTML5-SPEC-SECTIONS [tabular-data]

Related Actions Items:

• ACTION-66 on Joshue O Connor to Joshue to collate information on what spec status is with respect to table@summary, research background on rationale for retaining table@summary as a valid attribute - due 2008-08-29, closed
• ACTION-76 on Chris Wilson to Create poll on issue-32, based on Joshue's page from action-66 - due 2009-01-31, closed
• ACTION-104 on Chris Wilson to Inquire about table summary and headers status at PFWG caucus on 2009-02-06 - due 2009-02-26, closed
• ACTION-126 on Sam Ruby to Send a call to the WG to update the Wiki page to adequately reflect both (all) viewpoints on summary, in prep. for a vote - due 2009-06-11, closed
• ACTION-111 on Sam Ruby to Send call to working group on summary to update wiki in preparation for vote - due 2009-06-18, closed
• ACTION-128 on Cynthia Shelly to Work with PF to find an owner for drafting @summary text proposal - due 2009-08-20, closed
• ACTION-136 on Matthew May to Send draft to the list, due in three weeks - due 2009-09-17, closed
• ACTION-145 on Cynthia Shelly to Write a Change Proposal for summary - due 2009-11-08, open

Related emails:

1. Re: {agenda} HTML WG telcon 2009-11-19: issues, action items, calls for consensus/proposals, task force reports (from oradnio@gmail.com on 2009-11-19)
2. Re: {agenda} HTML WG telcon 2009-11-19: issues, action items, calls for consensus/proposals, task force reports (from laura.lee.carlson@gmail.com on 2009-11-19)
3. {agenda} HTML WG telcon 2009-11-19: issues, action items, calls for consensus/proposals, task force reports (from Paul.Cotton@microsoft.com on 2009-11-18)
4. {agenda} HTML WG telcon 2009-11-19: issues, action items, calls for consensus/proposals, task force reports (from Paul.Cotton@microsoft.com on 2009-11-18)
5. We have a volunteer to write a Change Proposal for ISSUE-32: table-summary (from mjs@apple.com on 2009-10-10)
6. minutes of 2009-10-01 telcon (from mike@w3.org on 2009-10-02)
7. Agenda for HTML WG telcon 2009-09-24 - CfCs, Accessibility TF, Testing TF, etc. (from mjs@apple.com on 2009-09-30)
8. [Bug 7633] The use of @summary should be encouraged when circumstances warrant (from bugzilla@wiggum.w3.org on 2009-09-29)
9. minutes for 2009-09-17 telcon (from mike@w3.org on 2009-09-20)
10. {agenda} HTML WG telcon 2009-09-17 (from rubys@intertwingly.net on 2009-09-16)
11. RE: [html] Summary draft (from jfoliot@stanford.edu on 2009-09-14)
12. Agenda for HTML WG telcon 2009-09-10 - Accessibility TF, Testing TF, etc (from Paul.Cotton@microsoft.com on 2009-09-09)
13. FW: Agenda for HTML WG telcon 2009-09-10 - Accessibility TF, Testing TF, etc (from Paul.Cotton@microsoft.com on 2009-09-09)
14. State of HTML WG Unresolved Issues (from mjs@apple.com on 2009-08-20)
15. {agenda} HTML WG telcon 2009-08-20 (from rubys@intertwingly.net on 2009-08-19)
16. {minutes} HTML WG telcon 2009-08-13 for review (from connolly@w3.org on 2009-08-13)
17. Re: Begin discussions for pushing Last Call into 2010 (from rubys@intertwingly.net on 2009-08-13)
18. Re: {agenda} HTML WG telcon 2009-08-13 (from cooper@w3.org on 2009-08-12)
19. Re: {agenda} HTML WG telcon 2009-08-13 (from singer@apple.com on 2009-08-12)
20. {agenda} HTML WG telcon 2009-08-13 (from rubys@intertwingly.net on 2009-08-12)
21. Re: Consolidated issues that may qualify as 'controversial' (from rubys@intertwingly.net on 2009-08-12)
22. Re: Consolidated issues that may qualify as 'controversial' (from jonas@sicking.cc on 2009-08-12)
23. Re: Consolidated issues that may qualify as 'controversial' (from shelleyp@burningbird.net on 2009-08-12)
24. Consolidated issues that may qualify as 'controversial' (from mjs@apple.com on 2009-08-12)
25. Re: summary attribute compromise proposal (from shelley.just@gmail.com on 2009-08-06)
26. RE: summary attribute compromise proposal (from jfoliot@stanford.edu on 2009-08-06)
27. Re: [DRAFT] Heartbeat poll - update 4 (from rubys@intertwingly.net on 2009-08-06)
28. minutes: HTML WG telecon 2009-08-06 [draft] (from julian.reschke@gmx.de on 2009-08-06)
29. Re: Thoughts regarding Maciej's compromise and the heartbeat publication (from rubys@intertwingly.net on 2009-08-05)
30. My position (was RE: [DRAFT] Heartbeat poll - update 2) (from jfoliot@stanford.edu on 2009-08-02)
31. RE: [DRAFT] Heartbeat poll (from jfoliot@stanford.edu on 2009-08-01)
32. RE: [DRAFT] Heartbeat poll (from jfoliot@stanford.edu on 2009-07-31)
33. RE: Publishing a new draft (HTML5+RDFa) (from jfoliot@stanford.edu on 2009-07-30)
34. Re: PROPOSAL: Procedure to Promote Progress With Accessibility Issues in HTML5 (from faulkner.steve@gmail.com on 2009-07-20)
35. Re: PROPOSAL: Procedure to Promote Progress With Accessibility Issues in HTML5 (from rubys@intertwingly.net on 2009-07-20)
36. RE: PROPOSAL: Procedure to Promote Progress With Accessibility Issues in HTML5 (from foliot@wats.ca on 2009-07-19)
37. minutes HTML weekly 9 July for review (from connolly@w3.org on 2009-07-09)
38. Re: PF Response: @Summary (from rubys@intertwingly.net on 2009-07-07)
39. Input on the agenda (from ian@hixie.ch on 2009-06-22)
40. Re: <font color='blue'> (was ISSUE-32) (from jonas@sicking.cc on 2009-06-19)
41. Input on the agenda (from ian@hixie.ch on 2009-06-15)
42. Re: <font color='blue'> (was ISSUE-32) (from rsayre@mozilla.com on 2009-06-15)
43. Re: <font color='blue'> (was ISSUE-32) (from rubys@intertwingly.net on 2009-06-15)
44. Re: <font color='blue'> (was ISSUE-32) (from jonas@sicking.cc on 2009-06-15)
45. Re: <font color='blue'> (was ISSUE-32) (from karl@la-grange.net on 2009-06-15)
46. Re: <font color='blue'> (was ISSUE-32) (from rubys@intertwingly.net on 2009-06-15)
47. Re: <font color='blue'> (was ISSUE-32) (from karl@la-grange.net on 2009-06-14)
48. Re: <font color='blue'> (was ISSUE-32) (from jonas@sicking.cc on 2009-06-14)
49. Re: <font color='blue'> (was ISSUE-32) (from shelley.just@gmail.com on 2009-06-14)
50. Re: <font color='blue'> (was ISSUE-32) (from rubys@intertwingly.net on 2009-06-14)
51. Re: <font color='blue'> (was ISSUE-32) (from shelley.just@gmail.com on 2009-06-14)
52. Re: <font color='blue'> (was ISSUE-32) (from joedwil@earthlink.net on 2009-06-14)
53. Re: <font color='blue'> (was ISSUE-32) (from rubys@intertwingly.net on 2009-06-14)
54. Re: <font color='blue'> (was ISSUE-32) (from rubys@intertwingly.net on 2009-06-14)
55. Re: <font color='blue'> (was ISSUE-32) (from jonas@sicking.cc on 2009-06-14)
56. Re: <font color='blue'> (was ISSUE-32) (from rsayre@mozilla.com on 2009-06-12)
57. Re: <font color='blue'> (was ISSUE-32) (from jonas@sicking.cc on 2009-06-12)
58. Re: What is the value of conformance? (was RE: <font color='blue'> (was ISSUE-32)) (from jonas@sicking.cc on 2009-06-12)
59. Re: <font color='blue'> (was ISSUE-32) (from rsayre@mozilla.com on 2009-06-12)
60. Re: <font color='blue'> (was ISSUE-32) (from jonas@sicking.cc on 2009-06-12)
61. Re: What is the value of conformance? (was RE: <font color='blue'> (was ISSUE-32)) (from rsayre@mozilla.com on 2009-06-12)
62. Re: <font color='blue'> (was ISSUE-32) (from jonas@sicking.cc on 2009-06-12)
63. Re: What is the value of conformance? (was RE: <font color='blue'> (was ISSUE-32)) (from bzbarsky@MIT.EDU on 2009-06-12)
64. RE: <font color='blue'> (was ISSUE-32) (from jfoliot@stanford.edu on 2009-06-12)
65. RE: <font color='blue'> (was ISSUE-32) (from jfoliot@stanford.edu on 2009-06-12)
66. Re: <font color='blue'> (was ISSUE-32) (from jonas@sicking.cc on 2009-06-12)
67. What is the value of conformance? (was RE: <font color='blue'> (was ISSUE-32)) (from jfoliot@stanford.edu on 2009-06-12)
68. Re: <font color='blue'> (was ISSUE-32) (from rsayre@mozilla.com on 2009-06-12)
69. Re: <font color='blue'> (was ISSUE-32) (from shelley.just@gmail.com on 2009-06-12)
70. Re: <font color='blue'> (was ISSUE-32) (from jonas@sicking.cc on 2009-06-12)
71. Re: <font color='blue'> (was ISSUE-32) (from rsayre@mozilla.com on 2009-06-12)
72. Re: <font color='blue'> (was ISSUE-32) (from jonas@sicking.cc on 2009-06-12)
73. RE: <font color='blue'> (was ISSUE-32) (from jfoliot@stanford.edu on 2009-06-12)
74. Re: <font color='blue'> (was ISSUE-32) (from rsayre@mozilla.com on 2009-06-12)
75. Re: <font color='blue'> (was ISSUE-32) (from Smylers@stripey.com on 2009-06-11)
76. Re: <font color='blue'> (was ISSUE-32) (from jgraham@opera.com on 2009-06-11)
77. Re: <font color='blue'> (was ISSUE-32) (from lhs@malform.no on 2009-06-10)
78. Re: <font color='blue'> (was ISSUE-32) (from jens@meiert.com on 2009-06-09)
79. Re: <font color='blue'> (was ISSUE-32) (from rubys@intertwingly.net on 2009-06-09)
80. Re: <font color='blue'> (was ISSUE-32) (from rsayre@mozilla.com on 2009-06-09)
81. Re: <font color='blue'> (was ISSUE-32) (from shelley.just@gmail.com on 2009-06-09)
82. Re: <font color='blue'> (was ISSUE-32) (from shelley.just@gmail.com on 2009-06-09)
83. Re: <font color='blue'> (was ISSUE-32) (from annevk@opera.com on 2009-06-09)
84. Re: <font color='blue'> (was ISSUE-32) (from murray@muzmo.com on 2009-06-09)
85. Re: <font color='blue'> (was ISSUE-32) (from lhs@malform.no on 2009-06-09)
86. Re: <font color='blue'> (was ISSUE-32) (from hober0@gmail.com on 2009-06-09)
87. Re: <font color='blue'> (was ISSUE-32) (from shelleyp@burningbird.net on 2009-06-09)
88. Re: <font color='blue'> (was ISSUE-32) (from lachlan.hunt@lachy.id.au on 2009-06-09)
89. Re: <font color='blue'> (was ISSUE-32) (from shelleyp@burningbird.net on 2009-06-09)
90. Re: <font color='blue'> (was ISSUE-32) (from lachlan.hunt@lachy.id.au on 2009-06-09)
91. Re: <font color='blue'> (was ISSUE-32) (from rsayre@mozilla.com on 2009-06-08)
92. RE: <font color='blue'> (was ISSUE-32) (from murray@muzmo.com on 2009-06-08)
93. Re: <font color='blue'> (was ISSUE-32) (from jonas@sicking.cc on 2009-06-08)
94. Re: <font color='blue'> (was ISSUE-32) (from jonas@sicking.cc on 2009-06-08)
95. RE: <font color='blue'> (was ISSUE-32) (from jfoliot@stanford.edu on 2009-06-08)
96. Re: {agenda} HTML WG telcon 2009-06-04 -- minutes enclosed (from singer@apple.com on 2009-06-04)
97. Re: {agenda} HTML WG telcon 2009-06-04 -- minutes enclosed (from singer@apple.com on 2009-06-04)
98. Input on the agenda (from ian@hixie.ch on 2009-06-01)
99. Re: Request for PFWG WAI review of summary for tabular data (from laura.lee.carlson@gmail.com on 2009-05-04)
100. Input on the agenda (from ian@hixie.ch on 2009-04-27)
101. Input on the agenda (from ian@hixie.ch on 2009-04-21)
102. Input on the agenda (from ian@hixie.ch on 2009-04-15)
103. Input on the agenda (from ian@hixie.ch on 2009-04-06)
104. Re: Input on the agenda (from rubys@intertwingly.net on 2009-04-01)
105. Input on the agenda (from ian@hixie.ch on 2009-03-31)
106. Input on the agenda (from ian@hixie.ch on 2009-03-24)
107. Input on the agenda (from ian@hixie.ch on 2009-03-16)
108. Input on the agenda (from ian@hixie.ch on 2009-03-09)
109. Re: summary='' in HTML5 ISSUE-32 (from jonas@sicking.cc on 2009-03-02)
110. Re: summary='' in HTML5 ISSUE-32 (from lhs@malform.no on 2009-03-02)
111. Re: summary='' in HTML5 ISSUE-32 (from lhs@malform.no on 2009-03-02)
112. Re: summary='' in HTML5 ISSUE-32 (from steveax@pobox.com on 2009-03-01)
113. Re: Draft text for summary attribute definition (from david.poehlman@handsontechnologeyes.com on 2009-03-01)
114. Re: Draft text for summary attribute definition (from rob@robburns.com on 2009-03-01)
115. Re: Draft text for summary attribute definition (from david.poehlman@handsontechnologeyes.com on 2009-03-01)
116. Re: Draft text for summary attribute definition (from lhs@malform.no on 2009-03-01)
117. Re: Draft text for summary attribute definition (from rob@robburns.com on 2009-02-28)
118. Re: summary='' in HTML5 ISSUE-32 (from lhs@malform.no on 2009-02-28)
119. Re: summary='' in HTML5 ISSUE-32 (from lhs@malform.no on 2009-02-28)
120. Re: summary='' in HTML5 ISSUE-32 (from rob@robburns.com on 2009-02-27)
121. Re: summary='' in HTML5 ISSUE-32 (from Smylers@stripey.com on 2009-02-27)
122. Re: summary='' in HTML5 ISSUE-32 (from poehlman1@comcast.net on 2009-02-27)
123. Re: summary='' in HTML5 ISSUE-32 (from julian.reschke@gmx.de on 2009-02-27)
124. Re: summary='' in HTML5 ISSUE-32 (from Smylers@stripey.com on 2009-02-27)
125. Re: summary='' in HTML5 ISSUE-32 (from Smylers@stripey.com on 2009-02-27)
126. Re: summary='' in HTML5 ISSUE-32 (from Smylers@stripey.com on 2009-02-27)
127. Re: summary='' in HTML5 ISSUE-32 (from mjs@apple.com on 2009-02-27)
128. Re: summary='' in HTML5 ISSUE-32 (from joshue.oconnor@cfit.ie on 2009-02-27)
129. Re: summary='' in HTML5 ISSUE-32 (from julian.reschke@gmx.de on 2009-02-27)
130. Re: summary='' in HTML5 ISSUE-32 (from joshue.oconnor@cfit.ie on 2009-02-27)
131. Re: summary='' in HTML5 ISSUE-32 (from lhs@malform.no on 2009-02-27)
132. Re: summary='' in HTML5 ISSUE-32 (from simonp@opera.com on 2009-02-27)
133. Re: summary='' in HTML5 ISSUE-32 (from ian@hixie.ch on 2009-02-27)
134. Re: summary='' in HTML5 ISSUE-32 (from ian@hixie.ch on 2009-02-27)
135. Re: summary='' in HTML5 ISSUE-32 (from lhs@malform.no on 2009-02-27)
136. Re: summary='' in HTML5 ISSUE-32 (from ian@hixie.ch on 2009-02-27)
137. Re: summary='' in HTML5 ISSUE-32 (from lhs@malform.no on 2009-02-27)
138. Re: summary='' in HTML5 ISSUE-32 (from rob@robburns.com on 2009-02-26)
139. Re: summary='' in HTML5 ISSUE-32 (from mjs@apple.com on 2009-02-26)
140. Re: summary='' in HTML5 ISSUE-32 (from rob@robburns.com on 2009-02-26)
141. Re: summary='' in HTML5 ISSUE-32 (from rob@robburns.com on 2009-02-26)
142. Re: summary='' in HTML5 ISSUE-32 (from mjs@apple.com on 2009-02-26)
143. Re: summary='' in HTML5 ISSUE-32 (from mjs@apple.com on 2009-02-26)
144. Re: summary='' in HTML5 ISSUE-32 (from rob@robburns.com on 2009-02-26)
145. Re: summary='' in HTML5 ISSUE-32 (from mattmay@adobe.com on 2009-02-26)
146. Re: summary='' in HTML5 ISSUE-32 (from P.Taylor@Rhul.Ac.Uk on 2009-02-26)
147. Re: summary='' in HTML5 ISSUE-32 (from ian@hixie.ch on 2009-02-26)
148. Re: summary='' in HTML5 ISSUE-32 (from ian@hixie.ch on 2009-02-26)
149. Re: summary='' in HTML5 ISSUE-32 (from mattmay@adobe.com on 2009-02-26)
150. Re: summary='' in HTML5 ISSUE-32 (from P.Taylor@Rhul.Ac.Uk on 2009-02-26)
151. Re: summary='' in HTML5 ISSUE-32 (from ian@hixie.ch on 2009-02-26)
152. Re: summary='' in HTML5 ISSUE-32 (from ian@hixie.ch on 2009-02-26)
153. Re: summary='' in HTML5 ISSUE-32 (from ian@hixie.ch on 2009-02-26)
154. Re: summary='' in HTML5 ISSUE-32 (from ian@hixie.ch on 2009-02-26)
155. Re: summary='' in HTML5 ISSUE-32 (from mattmay@adobe.com on 2009-02-26)
156. Re: summary='' in HTML5 ISSUE-32 (from julian.reschke@gmx.de on 2009-02-26)
157. Re: summary='' in HTML5 ISSUE-32 (from poehlman1@comcast.net on 2009-02-26)
158. Re: summary='' in HTML5 ISSUE-32 (from mjs@apple.com on 2009-02-26)
159. Re: summary='' in HTML5 ISSUE-32 (from mjs@apple.com on 2009-02-26)
160. Re: summary='' in HTML5 ISSUE-32 (from mattmay@adobe.com on 2009-02-26)
161. Re: summary='' in HTML5 ISSUE-32 (from connolly@w3.org on 2009-02-26)
162. Re: summary='' in HTML5 ISSUE-32 (from lhs@malform.no on 2009-02-26)
163. Re: summary='' in HTML5 ISSUE-32 (from P.Taylor@Rhul.Ac.Uk on 2009-02-26)
164. Re: summary='' in HTML5 ISSUE-32 (from mjs@apple.com on 2009-02-26)
165. Re: summary='' in HTML5 ISSUE-32 (from P.Taylor@Rhul.Ac.Uk on 2009-02-26)
166. Re: summary='' in HTML5 ISSUE-32 (from mjs@apple.com on 2009-02-26)
167. Re: summary='' in HTML5 ISSUE-32 (from mjs@apple.com on 2009-02-26)
168. minutes: HTML WG Weekly 26 Feb 2009 (from connolly@w3.org on 2009-02-26)
169. minutes: HTML WG Weekly 26 Feb 2009 (from connolly@w3.org on 2009-02-26)
170. Re: summary='' in HTML5 ISSUE-32 (from lhs@malform.no on 2009-02-26)
171. Re: summary='' in HTML5 ISSUE-32 (from connolly@w3.org on 2009-02-26)
172. Re: summary='' in HTML5 ISSUE-32 (from pjt47@cam.ac.uk on 2009-02-26)
173. Re: summary='' in HTML5 ISSUE-32 (from faulkner.steve@gmail.com on 2009-02-26)
174. Re: summary='' in HTML5 ISSUE-32 (from faulkner.steve@gmail.com on 2009-02-26)
175. Re: summary='' in HTML5 ISSUE-32 (from jgraham@opera.com on 2009-02-26)
176. Re: summary='' in HTML5 ISSUE-32 (from ian@hixie.ch on 2009-02-26)
177. Re: summary='' in HTML5 ISSUE-32 (from faulkner.steve@gmail.com on 2009-02-26)
178. Re: summary='' in HTML5 ISSUE-32 (from ian@hixie.ch on 2009-02-26)
179. Re: summary='' in HTML5 ISSUE-32 (from faulkner.steve@gmail.com on 2009-02-26)
180. Re: summary='' in HTML5 ISSUE-32 (from simonp@opera.com on 2009-02-26)
181. Re: summary='' in HTML5 ISSUE-32 (from ian@hixie.ch on 2009-02-26)
182. Re: summary='' in HTML5 ISSUE-32 (from faulkner.steve@gmail.com on 2009-02-26)
183. Re: summary='' in HTML5 ISSUE-32 (from joshue.oconnor@cfit.ie on 2009-02-26)
184. Re: summary='' in HTML5 ISSUE-32 (from faulkner.steve@gmail.com on 2009-02-26)
185. Re: summary='' in HTML5 ISSUE-32 (from simonp@opera.com on 2009-02-26)
186. Re: summary='' in HTML5 ISSUE-32 (from poehlman1@comcast.net on 2009-02-26)
187. Re: summary='' in HTML5 ISSUE-32 (from simonp@opera.com on 2009-02-26)
188. Re: summary='' in HTML5 ISSUE-32 (from faulkner.steve@gmail.com on 2009-02-26)
189. Re: summary='' in HTML5 ISSUE-32 (from poehlman1@comcast.net on 2009-02-26)
190. Re: summary='' in HTML5 ISSUE-32 (from faulkner.steve@gmail.com on 2009-02-26)
191. Re: summary='' in HTML5 ISSUE-32 (from ian@hixie.ch on 2009-02-26)
192. Re: summary='' in HTML5 ISSUE-32 (from lhs@malform.no on 2009-02-26)
193. Re: summary='' in HTML5 ISSUE-32 (from mjs@apple.com on 2009-02-25)
194. Re: summary='' in HTML5 ISSUE-32 (from joshue.oconnor@cfit.ie on 2009-02-25)
195. Re: summary='' in HTML5 ISSUE-32 (from gez.lemon@gmail.com on 2009-02-25)
196. Re: summary='' in HTML5 ISSUE-32 (from poehlman1@comcast.net on 2009-02-25)
197. Re: summary='' in HTML5 ISSUE-32 (from poehlman1@comcast.net on 2009-02-25)
198. Re: summary='' in HTML5 ISSUE-32 (from mattmay@adobe.com on 2009-02-25)
199. RE: summary='' in HTML5 ISSUE-32 (from sailesh.panchang@deque.com on 2009-02-25)
200. Re: summary='' in HTML5 ISSUE-32 (from faulkner.steve@gmail.com on 2009-02-25)
201. Re: summary='' in HTML5 ISSUE-32 (from mjs@apple.com on 2009-02-25)
202. Re: summary='' in HTML5 ISSUE-32 (from jonas@sicking.cc on 2009-02-25)
203. Re: summary='' in HTML5 ISSUE-32 (from poehlman1@comcast.net on 2009-02-25)
204. Re: summary='' in HTML5 ISSUE-32 (from jonas@sicking.cc on 2009-02-25)
205. Re: summary='' in HTML5 ISSUE-32 (from poehlman1@comcast.net on 2009-02-25)
206. Re: summary='' in HTML5 ISSUE-32 (from jonas@sicking.cc on 2009-02-25)
207. Re: summary='' in HTML5 ISSUE-32 (from poehlman1@comcast.net on 2009-02-25)
208. Re: summary='' in HTML5 ISSUE-32 (from rubys@intertwingly.net on 2009-02-25)
209. Re: summary='' in HTML5 ISSUE-32 (from jonas@sicking.cc on 2009-02-25)
210. Re: summary='' in HTML5 ISSUE-32 (from poehlman1@comcast.net on 2009-02-25)
211. Re: summary='' in HTML5 ISSUE-32 (from poehlman1@comcast.net on 2009-02-25)
212. Re: summary='' in HTML5 ISSUE-32 (from jonas@sicking.cc on 2009-02-25)
213. Re: summary='' in HTML5 ISSUE-32 (from mjs@apple.com on 2009-02-25)
214. Re: summary='' in HTML5 ISSUE-32 (from poehlman1@comcast.net on 2009-02-25)
215. Re: summary='' in HTML5 ISSUE-32 (from mjs@apple.com on 2009-02-25)
216. Re: summary='' in HTML5 ISSUE-32 (from janina@rednote.net on 2009-02-25)
217. Re: summary='' in HTML5 ISSUE-32 (from janina@rednote.net on 2009-02-25)
218. Re: summary='' in HTML5 ISSUE-32 (from wloughborough@gmail.com on 2009-02-25)
219. Re: summary='' in HTML5 ISSUE-32 (from rubys@intertwingly.net on 2009-02-25)
220. Re: summary='' in HTML5 ISSUE-32 (from poehlman1@comcast.net on 2009-02-25)
221. Re: summary='' in HTML5 ISSUE-32 (from rubys@intertwingly.net on 2009-02-25)
222. Re: summary='' in HTML5 ISSUE-32 (from rob@robburns.com on 2009-02-25)
223. minutes: HTML WG telecon 2009-02-19 [draft] (from julian.reschke@gmx.de on 2009-02-19)
224. minutes: HTML WG telecon 2009-02-10 [draft] (from oedipus@hicom.net on 2009-02-12)
225. Re: revised table headers design is OK, right? (from chaals@opera.com on 2009-02-11)
226. revised table headers design is OK, right? (from connolly@w3.org on 2009-02-11)
227. head@profile: another dropped attribute (from masinter@adobe.com on 2009-02-04)
228. RE: table-summary argument (from masinter@adobe.com on 2009-02-03)
229. table-summary argument (from masinter@adobe.com on 2009-02-03)
230. minutes: HTML WG weekly telcon 22 Jan 2009 (from connolly@w3.org on 2009-01-23)
231. minutes: HTML Weekly Teleconference 15 Jan 2009 (from connolly@w3.org on 2009-01-16)
232. Table feedback (from ian@hixie.ch on 2008-12-20)
233. Re: toward a schedule of HTML WG issues (from connolly@w3.org on 2008-08-22)
234. Re: toward a schedule of HTML WG issues (from julian.reschke@gmx.de on 2008-08-22)
235. toward a schedule of HTML WG issues (from connolly@w3.org on 2008-08-21)
236. {minutes} HTML WG issue-tracking telcon 2008-06-26 (from mike@w3.org on 2008-07-09)
237. {minutes} HTML WG issue-tracking telcon 2008-06-19 (from mike@w3.org on 2008-06-25)
238. {minutes} HTML WG issue-tracking telcon 2008-06-12 (from mike@w3.org on 2008-06-19)
239. Re: several messages about tables and related subjects (from ian@hixie.ch on 2008-03-23)
240. ISSUE-32 (table-summary): Include a summary attribute for tables? [HTML 5 spec] (from sysbot+tracker@w3.org on 2008-02-07)

Related notes:

Display change log