- From: Boris Zbarsky <bzbarsky@MIT.EDU>
- Date: Wed, 06 Oct 2010 10:33:33 -0400
- To: Daniel Glazman <daniel.glazman@disruptive-innovations.com>
- CC: HTML WG <public-html@w3.org>
On 10/6/10 5:54 AM, Daniel Glazman wrote: > <!ELEMENT table > (caption?, (col*|colgroup*), thead?, tfoot?, (tbody+|tr+))> > > while they are defined as the following in HTML 4 > > <!ELEMENT TABLE - - > (CAPTION?, (COL*|COLGROUP*), THEAD?, TFOOT?, TBODY+)> > > has always been a flaw in the model, where xhtml1 tables cannot > be output in html4. html5 has decided to solve the issue allowing > the max instead of narrowing on the min. HTML5 changes absolutely nothing in this area. Tables in text/html end up with the content model of HTML4; those in XML documents end up with whatever you stick inside them. What resolution are you looking for here, exactly? Making <table> containing <tr> directly in XML a validity error? Changing the parsing rules for XML? Something else? > As an editor implementor, this will drastically complexify my tables implementation. If your editor has to deal with XHTML, it already has to handle arbitrary children of <table>, no matter what HTML5 says, no? > Instead of always having a section container for a table row, I have to deal > with cases where such a container does not exist. Yep. So do browsers. It's annoying, for sure. Care to offer an alternative? -Boris
Received on Wednesday, 6 October 2010 14:50:08 UTC