- From: James Graham <jgraham@opera.com>
- Date: Thu, 11 Jun 2009 15:58:12 +0200
- To: Leif Halvard Silli <lhs@malform.no>
- CC: HTMLWG <public-html@w3.org>
Leif Halvard Silli wrote: > Leif Halvard Silli On 09-06-10 17.29: >> James Graham On 09-06-10 17.12: >>> Leif Halvard Silli wrote: >> >>>>> As a child of <table> <summary> (or any other element) has too bad >>>>> legacy compatibility properties to work. >> >>> I discussed the issues here: >>>> >>>> http://www.w3.org/mid/4A2DC7A6.206@malform.no > >>> The statement that this solution is fully workable ignores the fact >>> that AT must be updated to understand the <figure> element implies a >>> relationship between the <figcaption> (or <legend>) and the table. > > The draft already specifies that UAs must accept "taint" inside > <table>[1]. A consequence of accepting taint would be that the <summary> > element becomes possible even in Webkit and Firefox. I'm not sure I understand. Table taining is about where whitespace gets inserted when the current element in a parser is a <table> element (i.e. whether it is inserted into the <table> or into the foster parent). I don't see how the presence or absence of table taint has any bearing on <summary>.
Received on Thursday, 11 June 2009 13:57:53 UTC