- From: Boris Zbarsky <bzbarsky@MIT.EDU>
- Date: Mon, 30 Apr 2012 02:10:54 -0400
- To: "Tab Atkins Jr." <jackalmage@gmail.com>
- CC: www-style@w3.org
On 4/30/12 1:52 AM, Tab Atkins Jr. wrote: > <div style='display:table-row'> > <span> > foo > <div style='display:table-cell'>bar</div> > foo > </span> > </div> > > The result is a table with one cell, containing an inline split around > another table. No, it's not. The result is a table with one cell, containing an inline which contains some text, then an inline-table, then more text. See CSS 2.1 section 17.2.1, item 3, sub-item 2. No inline splitting going on here. Well, except in WebKit, which is just buggy; the spec on this is very clear and everyone else gets it right. See https://bugs.webkit.org/show_bug.cgi?id=15365 for details, such as they are. > This might technically be proving something slightly different No comment. ;) > but it's good enough for me. <shrug>. You're imposing a new restriction on the CSS processing model that wasn't there before. In particular, the new setup requires work that could have been done in parallel before to be done serially. This is _probably_ ok in this case, because for flexbox we have to define some ordering on this stuff anyway, but it's not obvious a priori what the right ordering is. -Boris
Received on Monday, 30 April 2012 06:11:24 UTC